Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Archive" of completed rooms such that when a new message is received the room is taken out of the archive #1705

Open
gabrc52 opened this issue Jan 8, 2024 · 8 comments
Labels
improvement An idea/future MSC for the spec

Comments

@gabrc52
Copy link

gabrc52 commented Jan 8, 2024

Suggestion

In many email clients there is an "Archive" feature, where users can either press a button or slide the email thread a certain way to signal that they are done with it and don't need to see it for the time being. Users can manually navigate to the archive to see these messages.

It would be nice to have this in Matrix. Of course, this would be best not as a client-side feature but stored in account data or somewhere various clients can all access and agree with each other on whwat is archived.

I was looking for example at mautrix/facebook#161 and some people outright leave rooms when they don't want to see them or are done with them for the time being, and have explicitly said they are doing it to have an email-like workflow.

This feature seems to be already available in the proprietary extended Matrix known as Beeper, but I could not find any MSC describing this:

image

This client seems to use a proprietary com.beeper.inbox.done room account data.

image

This is how the UI looks like, with only unarchived messages showing up in the "Inbox".

Some issues with this could be that there may be multiple ideas on implementation or how the feature should work. For example, WhatsApp is configurable so you can either:

  1. all archived chats are chats I don't really want to see unless I go to the archive
  2. I am archiving chats because I don't want to see them for the time being (I have responded, or I don't need to respond, etc) but will need to see it again once new messages show up

I believe 1) should already be met by the "low priority" tag implemented by Element and mentioned in the spec:

{
  "type": "m.tag",
  "content": {
    "tags": {
      "m.lowpriority": {}
    }
  }
}

so this issue would be about some sort of m.archive tag that disappears when a new message is received.

@gabrc52 gabrc52 added the improvement An idea/future MSC for the spec label Jan 8, 2024
@Mikaela
Copy link

Mikaela commented Jan 8, 2024

Elements have an issue about archives at element-hq/element-meta#1402 and I have opened feature requests about the Beeper behaviour at element-hq/element-meta#2053 and krille-chan/fluffychat#576.

@turt2live
Copy link
Member

By default in the specification a room is "archived" upon leaving. It must be forgotten to be removed from that archive.

Some servers treat leaving as forgetting, enabling cleanup functions.

@turt2live turt2live closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2024
@turt2live
Copy link
Member

(there's also Low Priority tags and Spaces which can help organize/temporarily hide rooms)

@HammyHavoc
Copy link

(there's also Low Priority tags and Spaces which can help organize/temporarily hide rooms)

Have you tried the archive function of WhatsApp?

It will hide something until it gets a new message as an option. Low priority and Spaces aren't a good solution. I've consolidated all my chat apps via bridges into Matrix, and navigating my list of conversations is terrible.

@gabrc52
Copy link
Author

gabrc52 commented Jan 8, 2024

What the spec calls "archived" Element (for example) calls "historical", and it is a different concept (rooms you've left or been kicked out of) from the one suggested in this issue.

In the spec, it might need to be called something different from "archived", but it would still make sense for some client implementations to call it "archive".

Putting rooms on a specific space would have the same drawback as "low priority" since they wouldn't be taken out of the space when a new message is received. We shouldn't put the burden on the users to remember about said chats.

@gabrc52 gabrc52 changed the title "Archive" room "Archive" of completed rooms such that when a new message is received the room is taken out of the archive Jan 8, 2024
@turt2live turt2live reopened this Jan 8, 2024
@DarkPhyber-hg
Copy link

Adding support for this. It makes sense for direct chats, or bridged chats (sms, google chat, fb/ig dm's, etc). Once a conversation is done, i may not want to "leave" it, but i also don't want to see it, it's distracting. I try to use a zero inbox philosophy with my chats/messages. If i need to do something i leave the chat visible, like my wife texted me to pick up milk. Otherwise, i hide/archive it to have less clutter.

@HammyHavoc
Copy link

Adding support for this. It makes sense for direct chats, or bridged chats (sms, google chat, fb/ig dm's, etc). Once a conversation is done, i may not want to "leave" it, but i also don't want to see it, it's distracting. I try to use a zero inbox philosophy with my chats/messages. If i need to do something i leave the chat visible, like my wife texted me to pick up milk. Otherwise, i hide/archive it to have less clutter.

Would also be nice to fav/star/"save" (ala MS Teams) individual messages to be able to come back to them to reply/action/reference. But yes, archiving is a must! My list room list is quite out of hand.

@gabrc52
Copy link
Author

gabrc52 commented May 5, 2024

If i need to do something i leave the chat visible

What I usually do is that if I need to do something I mark it as unread, but that is also missing from Matrix... #612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement An idea/future MSC for the spec
Projects
None yet
Development

No branches or pull requests

5 participants