matrix-org / matrix-org/matrix-spec
Support arbitrary metadata on invites (SPEC-357)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
A request from [~Rugvip] is to support the ability to include arbitrary metadata in invites, so that clients can perform business logic on the invite without having to accept it. The given example is:
let's say you're creating an online game on top of synapse, and you can invite users either to chat channels or to game lobbies
and if a room is a game lobby or not is determined by a key in the create state
You could of course do it with weird hacks in the room name, avatar, w/e
or what the hell, why not just make the invite state types configurable? :D
defaulting to the current ones
(Imported from https://matrix.org/jira/browse/SPEC-357)
(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
Review the invite-state requirements in the Matrix specification and the imported SPEC-357 request first. Clarify the metadata format, scope, compatibility requirements, and affected specification sections; done means the proposal is specified precisely enough for clients to use and the required specification updates are complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100