Specifically, in the screenshot shown, the response is shown as 404 OK instead of 404 Not Found.

Sure, I understand your concern.

Ah right.

Yeah, I don't think this is unique to Passphrase.

• Clicking on "Edit Credential" (which is greyed out) returns the "You Shall Not Pass" dialog.
• Clicking on "Allow Conduit Access" (which is not greyed out) also returns the "You Shall Not Pass" dialog.
• So shouldn't "Allow Conduit Access" be greyed out as well?

Its unexpected that these show as links I think? FacebookPOC, for example, is not a link.

Specifically, I would expect to see something like this:

Ah damn, so I can't accumulate a mountain of wealth through tokens :P

Not sure if you guys have seen this before:

Yeah, I get that. Happy to help test it out and give early feedback

I'm loving this by the way.

Testing from Gmail web client.

This seems relevant: https://mathiasbynens.be/notes/gmail-plain-text

Hmm, interesting. I sent this from the Gmail app for Android.

I am just sending this email in an attempt to reproduce this behavior.
Hopefully it reproduces on this install.

I was just curious as to what it would do... I'm happy for this to be closed as "Wontfix".

OK, thanks for clarifying.

I'm not sure that I understand...

https://secure.phabricator.com/differential/diff/28848/

I could provide you with a raw diff if that helps?

Not quite, see https://secure.phabricator.com/xhprof/profile/PHID-FILE-i37p3oetbxkqjt2fs35h/.

Instead of full URLs, couldn't the daemons determine whether or not to create transactions/mentions based on phabricator.uri from the project's .arcconfig file?

I have also looked at D11949.

In T7444#99690, @chad wrote:

The problem with the old design is it has a number of display issues, bad font mixing, and the different colors were problematic. One way to keep the header connected would likely involve removing the color choices.

Interestingly the format seems inconsistent with email now too.

Im not sure if its consistent, but I liked the boxing that previously joined the header to the code block. It made it obvious that the two were related.

I think this is purely an Arcanist thing.

I suppose that an SSH client for Conduit would mitigate this issue (T550).

Let me update the description on this ticket to provide more context, I filed it real quick so that I wouldn't forget about it.

In T7412#99096, @epriestley wrote:

I also think it would probably be reasonable to do this:

• If a configuration file like .arclint is not executable, read the file content to load configuration.
• If a configuration file like .arclint is executable, execute it. Read stdout to load configuration.

Not quite. The main issue I have is that the file is larger than the maximum configured size that nginx/PHP will handle. My solution in the past has been to I crease the nginx/PHP limits.

In T7408#99038, @Mnkras wrote:

Is this to get rid of deprecated functions/workarounds for older php versions or is this more of "I want to use these newer PHP functions and not worry about this old stuff and backwards compatibility"?

Potential code base changes that could be used after dropping support for PHP 5.2:

In particular, PHP 5.2 has a bunch of known security vulnerabilities.