MSC4333: Room state API for moderation bots #4333
Conversation
turt2live
changed the title
turt2live
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Client
- Moderation bot
There was a problem hiding this comment.
WIP as of writing, but moderation bot exists here: the-draupnir-project/Draupnir#944
Also WIP as of writing, client is here: element-hq/element-web#30648
| bot commands and a new state event published in the moderation bot's management room. | ||
|
|
||
|
|
||
| ## Proposal |
There was a problem hiding this comment.
TODO: Describe why we go with the commands approach instead of something else. The short version is we could support HTTP APIs, toDevice, custom event types (this one is mentioned briefly later), toWidget, etc, but commands are universally easy to support and hook up per MSC4332.
| then sent to the management room (instead of calling the `/ban` API, for example). | ||
|
|
||
|
|
||
| ## Potential issues |
There was a problem hiding this comment.
Draupnir in the future is going to require a --no-confirm flag for the ban command. I think if we spot that the org.matrix.msc4332.commandmixin is used in an event that we will have to pretend the --no-confirm flag is present.
2 participants
Rendered
Disclosure: I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published in my capacity as Tech Lead for T&S, though does not achieve any particular T&S project/goal.