matrix-org / matrix-org/matrix.to
Deprecate matrix.to for FediLinks
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
[The Fedi Links project](https://fedilinks.org/) is a project to introduce URI fallbacks in spite of OS/browser/client support. The main specification for the fallback behaviour is https://fedilinks.org/2 .
It would be neat to deprecate matrix.to entirely, tho we recognize that's a few years off. A good start would be to decide on what a hypothetical web+matrix URI should look like. Ideally, a web+matrix URI fallback would support viewing public rooms as a guest if the server allows for it, directly on the home server. This would help bridge the world of matrix with the world of the web.
Plus, what happens if the project dies/runs out of funding/gets bought out? A native fallback cannot be controlled, while matrix.to can be killed. Deprecating matrix.to would help with the [bus factor](https://en.wikipedia.org/wiki/Bus_factor).
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 Fedi Links specification at https://fedilinks.org/2 and the issue's discussion of a hypothetical web+matrix URI. Define a proposed URI shape, how it would support guest viewing of public rooms on the home server, and what deprecating matrix.to would require; done means the proposal is documented and agreed upon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100