element-hq / element-hq/element-meta
It's not ideal that new 3PID mappings silently clobber old ones
Open
Nobody has claimed this yet.
A-3PIDs
A-Registration
O-Uncommon
S-Major
T-Defect
- Dominant language
- No language data
- Stars
- 112
- Forks
- 26
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 4
Description
e.g. if I auth my MSISDN with a random Matrix account, it silently replaces the previous mapping without telling me
Contributor guide
No contributing guide indexed for this repository
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 3PID mapping handling described in the issue and trace what happens when an MSISDN is authenticated to a different Matrix account. Clarify whether the desired outcome is a warning, rejection, or another policy; done should include an explicit outcome for an existing mapping rather than silent replacement.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100