Automatic .well-known/matrix/support creation #812

Closed
opened 2025-04-30 18:37:19 +00:00 by Jade · 4 comments
Owner

We already know all the server admins, automatically exposing this via the support enpoint would help make sure more homeservers are contactable. Additionally, providing an easy way of configuring this, like we do for client/server, would be good.

We already know all the server admins, automatically exposing this via the support enpoint would help make sure more homeservers are contactable. Additionally, providing an easy way of configuring this, like we do for client/server, would be good.
Jade added the
Enhancement
label 2025-04-30 18:37:19 +00:00
Owner

This conflicts with the config options, does it not? or would this only apply when manually unspecified?

This conflicts with the config options, does it not? or would this only apply when manually unspecified?
Author
Owner

This would only apply when unspecified.

Side note, we need to document these config options. Possibly set it to allow setting an array for the roles, because it only allows setting one at a time right now.

This would only apply when unspecified. Side note, we need to document these config options. Possibly set it to allow setting an array for the roles, because it only allows setting one at a time right now.
nex added the
Matrix/Administration
label 2025-04-30 23:16:34 +00:00
Owner

If we wanted to be really cool, we could make it so users can DM the admin bot, and their messages will be passed on to the admin room, like some sort of ad-hoc honoroit, and then list the admin bot in the automatically generated support contacts. That's a lot more work though, so likely something to consider after implementing this.

If we wanted to be really cool, we could make it so users can DM the admin bot, and their messages will be passed on to the admin room, like some sort of ad-hoc [honoroit](https://github.com/etkecc/honoroit), and then list the admin bot in the automatically generated support contacts. That's a lot more work though, so likely something to consider after implementing this.
Owner

Implemented in #833

Implemented in #833
nex closed this issue 2025-05-26 01:38:32 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#812
No description provided.