matrix-org / matrix-org/matrix-spec

Consider more transactional APIs for things like promoting/demoting members in a room

Open
#446 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-Client-Server enhancement
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

To avoid cases where someone accidentally gets promoted then demoted again because the client has to send the whole state event. Servers could handle this more cleanly if there were endpoints for setting an individual's power level in a room.

Other APIs might benefit from a similar change.

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

No files or tests are named. Start by reviewing the room power-level state-event API described in the specification and identify the client race this proposal addresses. Done would require a decided, scoped design for transactional member power-level endpoints and any related APIs.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.