matrix-org / matrix-org/matrix-bifrost
If a profile doesn't exist for a remote user, we won't route DMs over the gateway interface
Open
Nobody has claimed this yet.
S-Minor
T-Defect
- Dominant language
- TypeScript
- Stars
- 187
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
We shouldn't assume a remote profile exists and should mock one up from the localpart if we need a displayname.
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 tracing gateway-interface DM routing and the remote profile lookup. Check how the remote user's localpart can supply a display name when no profile exists. Done means direct messages route successfully through the gateway without requiring a remote profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100