matrix-org / matrix-org/matrix-spec

Publicly advertise bridged accounts and rooms

Open
#620 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-Application-Services feature
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

(part of my secret masterplan for awesome bridging and leveraging existing networks)

I want to be able to use matrix while my friends still use their IM service of choice.
I want to be able to send them a matrix.to link instead of worrying about which messenger they prefer.

For easy discovery, we need to have standard ways of doing the following:
1. [ ] Allow bridges to automatically advertise the bridged account on the identity server for [bridged] -> [mxid]
2. [ ] Allow bridges to automatically advertise the bridged account in the profile for [mxid] -> [bridged]
3. [ ] Enable matrix.to (and other messengers) to read and display public profile information.
4. [ ] Same thing goes for rooms! There should be a standardized way for rooms to advertise publicly what they're bridged to. (maybe even for non-public rooms)
5. [ ] And we probably need a room directory search on the web for people who don't yet have a matrix account, but who might want to join in on the fun through bridged channels.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Matrix specification areas covering identity servers, profiles, room directories, matrix.to links, and bridge discovery. Map the five requested discovery mechanisms and determine the standardized protocol behavior needed for bridged accounts and rooms; done means the scope and interoperable requirements are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.