Skip to content

Always remember read state in MUCs #855

Description

@foss-

What would you like to see?

Currently all MUCs are marked read on launch. This behavior is problematic for chats which are relevant and require the user to be aware of all messages. E.g. work chats or focus groups of a handful of people instead of the random "everything android" MUC with several hundred people in it.

There will always be scenarios where for a certain MUC a user may not want to lose read state by just launching a chat client.

What problem does this solve?

Whichever solution is implemented it is problematic taking last read marker away from users on load. That should be prevented. Implementing #851 will help with anxiety of too many messages. Just tap esc key and mark room read. This is how Matrix, Rocket.Chat and others have it implemented and imo makes sense.

Proposed solution

To avoid losing read state marker on load, there are a few ways this could be handled. It was mentioned that Slack, while initially showing the latest message, has an UI option to quickly jump to last read marker in timeline. That seems like a solution satisfying both sides.

Telegram does it vice verse: loads last read marker and has an UI option to quickly jump to latest message.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions