matrix-org / matrix-org/matrix-spec
If an appservice has a non-exclusive alias field in it's namespace, does that alias trigger /_matrix/app/v1/room requests?
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
Basically, are non-exclusive aliases passive (and can be created by an appservice, but non-existent aliases are not handled by an appservice).
The spec is currently unclear.
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
Review the specification's appservice namespace and the /_matrix/app/v1/room request behavior described in the issue. Determine how non-exclusive aliases should behave, then clarify that behavior in the relevant specification text and verify that the ambiguity is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100