Skip to content

interactions between draft/read-marker and non-persistent clients are confusing #2374

@slingamn

Description

@slingamn

If the user is not always-on, but is using a client that supports MARKREAD, their read markers won't be saved, so every time they get fully logged out and back in, they'll see all messages in all buffers as unread, which is undesirable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions