Still needs work:

I don't currently plan to pursue this. We haven't seen interest from other installs and I think the upstream behavior is reasonably good most of the time and not a huge issue even when we get it wrong (you can still review the file without doing anything, and can get highlighting with a few clicks -- plus, the file and page render much faster).

• The secret $1-2,7-9 syntax for highlighting multiple noncontiguous blocks of lines in Diffusion is no longer supported.

A related attack is a bare whatever.patch file which writes to .git/config or .hg/hgconfig or whatever.

In Safari we get this marvel:

This will ultimately be covered by T13105.

Effectively now covered by T13105.

See T13105 for browse cases (and perhaps diff cases, eventually).

• If a file is non-UTF8, we should try the repository's "Encoding" as a default (or maybe just remove this feature).

Junk I'm about to break in Diffusion (but plan to restore):

I don't currently plan to pursue this.

We now support emoji; we might support stickers at some point. If we did, I'd expect them to use the autocomplete element (which I think is in a relatively good place for emoji), not actually be invoked with :P, ^-^, etc.

Since there's no known actual problem with this today, I don't plan to fix it.

This is well-suited to a third-party extension, particularly after T5055.

I don't currently plan to pursue this.

I don't currently plan to pursue this.

I don't currently plan to pursue this.

I don't currently plan to support this.

I don't currently plan to support this. You may be able to add a rule to support something like <br /> with a Remarkup extension.

I don't currently plan to change the remaining edge case behaviors since I'm not sure they ever occur in the wild.

This seems largely resolved.

This request seems very niche, so I don't currently plan to pursue this. It may be possible to implement it as an extension.

I don't currently plan to pursue this.

This is unlikely to ever happen without stronger use cases for nested block-level elements.

See T13110 for some followups.

This script can back-populate revision sizes that haven't been updated since D18832:

where I plan to explore the [----++ ] element

Some states:

• shouldBroadcast() has been removed; getShouldBroadcast() now means the same thing.

• getHasBroadcast(), setHasBroadcast(), and PROPERTY_HAS_BROADCAST are now getShouldBroadcast(), etc.

• Implementing BuildableInterface now requires implementing newBuildableEngine().
• Implementing BuildableInterface no longer requires implementing getHarbormasterPublishablePHID(). Publishing indirection is now handled by BuildableEngine.
• PhabricatorTransactions::TYPE_BUILDABLE no longer exists. Instead, applications should implement application-specific modular transactions to report build status information. DiffusionCommitBuildableTransaction may be useful as a template.

I'd like to analyze data on the $5 tier with an eye to removing it. Anecdotally, this doesn't seem to be doing anything good for us ... It also feels like we have a lot of $5 test instances.

The UI and allocation logic for shards need tweaking.