matrix-org / matrix-org/matrix-spec
HS should be able to announce what URIs they can gateway (SPEC-201)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
When designing the AS API (somewhere in the guts of https://github.com/matrix-org/matrix-doc/pull/5 or an associated etherpad) Kegan and I discussed the idea of homeservers being able to advertise the capabilities of the ASes they have configured - especially if those ASes can act as a gateway to another network. This in turn could be useful for clients to be able to 'do the right thing' automatically if asked to join a foreign URI, assuming they know what servers are available.
This might involve advertising capabilities via well-known URIs (https://github.com/matrix-org/matrix-doc/issues/433), tracking how URI->MXIDs are converted (https://github.com/matrix-org/matrix-doc/issues/436), or the stuff which is meant to advertise what URIs a given room is bridged to (https://github.com/matrix-org/matrix-doc/issues/439).
(Imported from https://matrix.org/jira/browse/SPEC-201)
(Reported by @ara4n)
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 discussion in matrix-doc PR 5 and the related issues 433, 436, and 439. Determine which mechanism should advertise homeserver gateway capabilities and how URI-to-MXID conversion and bridged-room URIs fit together. Done means the chosen behavior is defined in the Matrix specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100