This is one great Wikimedia patch being upstreamed. Should I make this a sub-task of T15081?

To me, "obsolete" manes "no longer appliable" - basically, "the information in this page doesn't apply any more".
Some (made up) examples:

• "Can Phorge run on PHP 7.0?" (The answer is no, because of a specific bug in 7.0, which was EOL a long time ago)
• "I have this problem in the Chatbot app" (We've deleted the chatbot app)

In T15450#16936, @Iniquity wrote:

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious

That's a good question. In general in Phorge/Phabricator any archived thing is editable. So I would say no, that archiving a chat still allows to write a message. But maybe it should not generate notifications.

Would sending messages be pevented on archived rooms and would all participants be removed (unless Can Edit is set to Room Participants)?

In T15237#14300, @valerio.bozzolan wrote:

I think a dedicated policy for "Can send messages" would be better, to cover more cases. It would be strange that all participants must also be allowed to edit all settings.

I have also noticed this issue when submitting updates to a revision -

Potentially related to Herald. Adding Herald to raise more attention.

I do not recommend, because https://phabricator.wikimedia.org/T293139 - Phorge displays whatever it gets, especially if the video got deleted in the meantime. Same behavior for Youtube.

(Additional context: as follow-up request, the most adopted token MUST always be "fox" or "🦊", forever - even if not available. So maybe the implementation is a bit simpler and efficient 👍 lol)

the vsts has a good workboard experience for this feature, it supply the mapping setting for the board relationship.

In T15100#18699, @aklapper wrote:

I'm not skilled enough to look into the bigger picture, however maybe the Edit Column dialog could have a third field apart from Name and Point Limit to also have Task Limit (or Card Limit?). Point Limit and Task Limit then must be mutually exclusive (do not allow to set both for a column, or even...board?), somehow.