matrix-org / matrix-org/matrix-spec
Supporting arbitrary small-scale 3rd party ID systems. (SPEC-149)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
I'm concerned that we've accidentally designed out the scenario where Bob has a cool app with an existing account DB in it - and wants to Matrix-enable his users.
Do they all have to go and manually sign up for separate Matrix accounts on a separate HS? Does he run a HS himself? Does he autoprovision these new accounts? (If so, the idea of one-matrix-id-per-user gets alarmingly broken) Does he force the user to enter their matrix HS details in order to link their existing app account to Matrix? Or a combination of the two, where their @username:bobsoft.com forwards through to @matthew:matrix.org?
It's critical that we let existing communities easily build on Matrix and get this story straight. Suggestions welcome.
(Imported from https://matrix.org/jira/browse/SPEC-149)
(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
No file, test, or entry point is identified in the issue. Start by reading the discussion and the imported SPEC-149 context; done means an agreed and documented Matrix approach for existing communities to link or provision third-party accounts.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100