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.

When this eventually moves forward, it's probably also appropriate to remove the syntax-highlighter.engine config option. I think this has essentially zero use in the wild and we have better modern patterns to approach the problem (without extreme-niche config options) if there are real-world use cases.

Oh, and I found the beast to get a portal to Saqawal's Roost and killed Saqawal and got the boots, but the boots and set in general seem kinda bad so they're sitting in one of my six tabs full of unique items that I will never ever sell or do anything with.

D19269 makes Harbormaster objects destructible. I've made Build destroy BuildMessage (which it doesn't receive, so this never destroys anything) but not BuildCommand (which it does receive), so that when this change is made (and it starts receiving BuildMessage instead of BuildCommand) things will just work. Until then, BuildCommand objects are technically left hanging, but destroying builds is exceptionally rare so I'm just assuming that this will probably be fixed before anyone notices.

I think this is sort of less bad/weird now, at least. You get a tokenizer instead, which is still empty, but you're prompted to "Type a repository name..." and the UI isn't this odd empty select thing anymore.

D19266 adds some additional Support Pact adventure mode content. Some other ideas for improving this mode: