matrix-org / matrix-org/matrix-spec
How can we enforce default permissions on a room (to prevent AS abuse) (SPEC-228)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Submitted by @matthew:matrix.org
There are situations where in order to interact with an AS, we want to either allow or deny users the ability to send or read AS-specific events (https://github.com/matrix-org/matrix-doc/issues/542). We currently have nowhere to do this. Perhaps it should be part of the AS API - to let ASes apply preset power thresholds (including per-event thresholds) to rooms which are created in the namespaces they subscribe to
(Imported from https://matrix.org/jira/browse/SPEC-228)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Matrix specification issue 542 and the application service API context described here. Define how an application service could set default room power thresholds, including per-event send or read permissions; done requires a clear, agreed specification for rooms created in subscribed namespaces.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100