MSC4121: m.role.moderator /.well-known/matrix/support role.

[FSG-Cat]

Rendered

This MSC gives homeservers the ability to split administration and moderation in their support records.

Signed-off-by: Catalan Lover catalanlover@protonmail.com

[turt2live]

Implementation requirements:

• Server publishing this information, preferably several servers.
• Client or consumer which uses and requires this information.

[aine-etke]

Implemented in msc1929 go client that is used by MRS (ref)

[girlbossceo]

Ruma "unstable" implementation for clients and servers to use: ruma/ruma#1768

Conduwuit implements an admin command to fetch /.well-known/matrix/support, and supports serving the file directly with the moderator role (or any other role).

[TheArcaneBrony]

Servers publishing this role:

• the-apothecary.club
• transfem.dev

Note: this is an incomplete list and there are probably more servers out there.

[TheArcaneBrony]

Real world use: some homeservers have 100% separation between administrators (server maintainers) and moderators (those who handle reports and appeals).

This distinction is generally due to wanting to have privacy for reports/appeals, which admins have no involvement in at all, and administrators shouldn't even know about moderation concerns.

Another example: etke.cc (matrixrooms.info developers & maintainers) would also benefit from this (administrator -> etke.cc as server admins, moderator -> instance staff).

[aine-etke]

Sounds as excellent case, and I'd propose to include it in the Proposal section of the MSC

administrator -> etke.cc as server admins

There is a misunderstanding - etke.cc handles only the system part of the server (OS-level, components deployments and configuration, etc.), we don't even have matrix user-level access to the customers' servers.

[TheArcaneBrony]

Yes, I know that, that's why I said server admins - you handle deployment and maintenance.