matrix-org / matrix-org/matrix-spec
Clarify how exclusive/inclusive appservice user namespaces work in terms of exposing details of a room
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
For example, the appservice can only query /joined_members if the appservice is querying with a user_id that is a resident of the room *and* part of an **exclusive** namespace
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 locating the appservice user-namespace and /joined_members sections in the Matrix specification. Read how exclusive and inclusive namespaces are currently described, then clarify the conditions for exposing room details, including the example in the issue. Done means the specification explicitly explains which namespace and room-membership combinations permit the query.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100