Skip to content

Refine and clarify how presence works #3797

Description

@ara4n

Documentation: https://docs.google.com/document/d/1sKaM9J5oorEeReYwOBmcgED6XnX2PdCYcx0Pp0gFnqM/edit#

Edited by TravisR to make this a proposal - original body below


The presence API is better than it used to be, but still very confusing in some respects. Custom presence is particularly broken, as @turt2live discovered in matrix-org/matrix-react-sdk#1676.

I've made a proposal at https://docs.google.com/document/d/1sKaM9J5oorEeReYwOBmcgED6XnX2PdCYcx0Pp0gFnqM/edit# - if someone can review it then I'll do a spec PR (and a synapse PR) to implement it. It will be largely backwards compatible with the current behaviour.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-Client ServerClient-Server APIT-Enhancementkind:maintenanceMSC which clarifies/updates existing specneeds-implementationThis MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP.proposalA matrix spec change proposal. Process state.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions