In T10745#229028, @chad wrote:

I'm not sure I follow what you're trying to tell us.

These types of e-mails are still being sent. Here's one from July 10, 2017:

In T11989#203781, @epriestley wrote:

Press F to pay respects.

In T12157#208851, @epriestley wrote:

This task does not capture abuse cases. If you'd like us to build anti-abuse tools, please file a separate request describing the abuse you're seeing. See also T10215.

This task got cross-referenced with https://phabricator.wikimedia.org/T115579. My impression of the Wikimedia Phabricator task was that we wanted a way for Phabricator admins to be able to edit the title of another user without needing to edit the database contents directly (cf. https://phabricator.wikimedia.org/T115579#2973336). I'm not sure this task captures that request.

In T5267#199144, @epriestley wrote:

• Did you notice that "Spanish (Spain)" was under the "Limited Translations" heading, instead of the "Translations" heading?

It looks like T10814, specifically T10814#170824, provide some useful info. Thank you for that link!

In T5267#198537, @chad wrote:

The current status is the infrastructure is provided, but the translations are not (you need to either translate it yourself, or check the community wiki page here for community contributed translations). Then install said translations locally.

I'd like to get this task un-stuck. I'm unclear on Phabricator's current internationalization capabilities.

In T10215#197805, @brechtvl wrote:

• Custom Blender specific captcha or question that bots can't answer

In T11471#190152, @epriestley wrote:

If you don't like the @mention-implies-CC behavior, you can disable it by applying this patch to your install:

[...]

In T11471#190079, @chad wrote:

I don't consider this to be a bug and any fix would likely lead to additional user confusion over "magic".

In T6502#187499, @dpaola2 wrote:

We have no precedents of abuse in Phabricator so far, but looking at our history with Bugzilla I will not be surprised the morning we find a first precedent.

^ I am incredibly jealous of your perspective and am really, really surprised you haven't had this problem yet!

I received this e-mail recently:

In T7643#179137, @epriestley wrote:

Diffs should be less choppy now, here's the improved version of the above change:

On the Wikimedia side, looking at https://phabricator.wikimedia.org/T1178, I see almost no support or consensus for this feature. Restricting open editing is in some ways antithetical to Wikimedia's values (we try to be as open as possible) and there are a lot of other issues with Phabricator that are higher priority for us.

I find this type of hasty task closure really off-putting and inappropriate. There are many parts of Phabricator and Phabricator development that I like, but this issue tracker is a little toxic.

In T4214#98858, @chad wrote:

Been thinking if we go back to the rainbow logo, no one will want to change it maybe?

In T5358#102327, @qgil wrote:

We are requesting a setting to allow our admins to disable Self Actions by default in our instance, because we know our community and this is what they are clearly asking for.

Linking this request to T4103 is conceptually correct, but here we are talking about a single system-wide binary setting that could be defined from the Configuration backend without any UI changes. T4103 encompasses a collection of rather rich features that will take a long time to start and complete, and that is currently prioritized as Wishlist. Maybe this was a way to say yes, but is pretty close to a no. :)

In T5358#101777, @epriestley wrote:

How about changing the entire product to default to not sending any email?

This issue is especially painful if users treat Phabricator Maniphest task descriptions as a drafting area. (Wikimedia migrated from Bugzilla, which had non-editable bug descriptions. Users have started to adapt to Phabricator's more open nature.)

I'm politely requesting a reconsideration of this ticket as I filed a similar task at https://phabricator.wikimedia.org/T914 and was pointed here.