matrix-org / matrix-org/matrix-spec
How does an exclusive namespace of room IDs even work?
Open
Nobody has claimed this yet.
A-Application-Services
clarification
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
The inverse of https://github.com/matrix-org/matrix-spec/issues/288 - if an appservice has an exclusive namespace of !.*, what does that mean? Can no one create a room? Can no one join a room?
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
Read this issue alongside Matrix spec issue #288, then locate the specification text defining exclusive appservice namespaces for room IDs. Clarify whether the namespace affects room creation, joining, or both, and update the relevant specification wording so the behavior is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100