Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

FSG-Cat
Copy link
Contributor

@FSG-Cat FSG-Cat commented Mar 22, 2024

Rendered

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

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

@FSG-Cat FSG-Cat changed the title MSCXXXX: m.role.moderator /.well-known/matrix/support role. MSC4121: m.role.moderator /.well-known/matrix/support role. Mar 22, 2024
@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Mar 22, 2024
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

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

Copy link

@etkecc etkecc Mar 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -0,0 +1,58 @@
# MSC4121: `m.role.moderator` `/.well-known/matrix/support` role.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants