matrix-org / matrix-org/matrix-spec

Bridges cannot determine if/when a user is deactived

Open
#769 0 comments 2 reactions 0 assignees View on GitHub
A-Application-Services
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

Which means things like IRC connections / presence on the remote room is kept forever. We need a way to signal to appservices that a user has been deactivated. One idea could be to include some metadata on the leave event for the user OR sending a synthetic event to the AS,

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the specification's appservice behavior and leave-event definitions, then trace how user deactivation is represented today. Done means the specification defines an unambiguous signal that appservices and bridges can use to detect deactivation and remove remote presence.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.