> why would this have violated community standards? Is there some rule about not mentioning "un-persons" or something?

Flags may be cast by anyone, and this will eventually result in automatic hiding - flags on Discourse are weighted according to the "trust level" of those raising them.

My guess is that people perceived this as a passive-aggressive objection to Tim Peters' suspension. It has definitely been permitted up until now to refer to this (although everyone seemed to be avoiding the name on principle), but there seems to be an expectation that people should "read the air" now and stop talking about it - hence posts like https://discuss.python.org/t/moderated-posts-are-no-longer-p... and https://discuss.python.org/t/pr-disaster-surrounding-recent-... .

> and sparking a call for a vote of no confidence in the council which did not succeed

The call was retracted, which is not surprising. The Steering Council isn't the root of the problem, anyway. That would be the Code of Conduct Work Group (https://www.python.org/psf/workgroups/#code-of-conduct-work-...), which is not elected (https://wiki.python.org/psf/ConductWG/Charter#Membership), has membership overlapping other important groups (4 of them are on the PSF Board of Directors - https://www.python.org/psf/board/#id3 - and Brett Cannon and Łukasz Langa are Discourse forum moderators) and enforces the Code of Conduct according to hidden rules that betray the neutrality of that document (https://policies.python.org/python.org/code-of-conduct/Enfor...) counter to the wishes of one of the original drafters of said document (https://discuss.python.org/t/why-i-am-withdrawing-fellowship... ; https://discuss.python.org/t/why-im-leaving-discuss-python-o... etc.).

It's also noteworthy that the Steering Council - consisting of 5 core devs - apparently also now requires a "communications liaison" (https://www.notion.so/46aec24028fd4e8dbdba003097c18b5b?pvs=2...) who gets a glowing write-up in official updates on the forum (such as https://discuss.python.org/t/steering-council-updates-for-ju...) - which are not posted by said liaison. I have no idea why this should be necessary, nor is there anything in PEP 13 (https://peps.python.org/pep-0013/) about this position existing. It seems that this person was selected entirely out-of-process.