This doesn't look like a bug in Phabricator; the reporting user is likely discussing client-side mail filtering rules which, by design, can never work against "Must Encrypt" mail.

Comment 3: Self mail on again.

Comment 2: Self mail off.

Comment 1: Self mail on.

A similar "attack" is to send a link to two destinations based on the viewer:

We haven't seen other interest in this and the use case feels a little unusual (I suspect 15-20% empty documents is very unusual) so I don't plan to implement it at this time.

I'll follow up with more details on what was accessed once we conclude our response.

See PHI372 -- setting user.custom-field-definitions (or, probably, any similar config) to a string will pass validation but then fatal in use.

No. Mail stamps are not intended to answer "Why am I receiving this mail?" in the general case (which lives in T9412 now, I think).

Example usage (for simplicity, requires at least one user named "Jake" on your install to function correctly):

After D19089, you can probably emit a projects(people-named-jake()) token or whatever and have it work for some values of "work" and "whatever". Tentatively, it doesn't look like this needs a lot of API changes, so I'm going to move forward with the simple version of the original request.

@avivey, heads up that I'm renaming PhabricatorQuickSearchEngineExtension to PhabricatorDatasourceEngineExtension. I'm leaving an empty subclass in master for now so that nothing breaks, but will delete it sooner or later, so rename QuickSearch to Datasource in your extends ... statements (and, ideally, class names) at some point before then to keep things working smoothly.

Quicksand isn't really bound by natural law, but I think that might fix it.

A workaround is to turn off the little inline chat thing so Quicksand disables itself, but this should be an easy fix.

We got a printer fax spam support request into the completely private Support app today. 😑

Phriction already has modular transactions, but does not have an EditEngine. That likely needs to happen first.

This never got fleshed out into an actionable plan, see T13077 for the next planned phase here.

I'm going to roll this into T13077, which will provide full access to Phriction via the API. In combination with Webhooks, you could mirror everything into some external read-only backup system or just pipe every edit to lp and stick it in a binder or something.

Mooted by the switch to prose diffing.

Rolling this forward into T13077.

We no longer offer free instances and I don't currently plan to offer them again, so this is moot.

We no longer offer free instances so tier growth is slower, and I plan to compact the tier in the nearish term.

We no longer offer free instances so I don't currently plan to pursue this.

We generally seem to have a reasonable handle on this after all.