-
Notifications
You must be signed in to change notification settings - Fork 380
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
MSC4206: Moderation policy auditing and context #4206
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation requirements:
- Client sending context
- Client using context
Alice can then send normal Matrix messages in the thread in | ||
order to provide any context, including screenshots. | ||
|
||
## Potential issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If m.policy.rule.context
is also meant to be a state event, existing chat clients might not be able to render the context thread as they likely won't support threading on state events. This might not be a terrible problem other than being able to browse context rooms from a non-specialized client possibly being convenient.
combination, then this step is skipped. | ||
|
||
Neighnir then creates a threaded message referring to the | ||
policy context. This step is skipped if a thread is already open. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it be expensive to find existing events in large policy lists given that you have to scan content
on every context event? The bot could possibly work around that by keeping its own index.
Rendered
Signed-off-by: Gnuxie Gnuxie@protonmail.com