I like #Matrix and #Signal both for group communications, but there are still many things that #email does much better. For example, I often want to quickly preview a message to see if I want to deal with it now. If not, then I leave it marked unread. Not possible all the messenger apps I've tried. That leads to slower response times because I won't open messages until I'm fully ready to deal with something more complicated. Maybe #DeltaChat is the best direction for the long term.
@eighthave strange idea being chat on email
@vitriolix I didn't know #Slack did that. I find Slack's UX to be over-complicated and put too much emphasis on emojis. But I also haven't used it that much. I worry about #Matrix going too much in that direction, but I would like to at least try a "preview then mark unread" UX in Matrix.
@eighthave Curious, how would you suppose Delta Chat could implement "mark-unread" in its UIs? Some of us recognize the use case underlying mark-unread (and use it on regular MUAs) but for a messenger-UX it's not easy to implement "mark-unread" -- maybe there is something better like marking a message with "todo" and having such marked messages appear in a special "todo" chat, and clicking them transfers you back to the chat-context of the message?
@delta Has anyone tried just adding a "mark unread" to a messenger UX? Seems worth trying. Like just long-press message, and choose "mark unread". I could see it also implemented something like "reset unread position to this point".
@eighthave @delta as much as I dislike Slack, they do this. Alt-click on web, long-press on mobile, then "Mark unread". It moves the "unread" line to just above the selected message in the chat/thread
@eighthave not easily possible to "just mark unread": usually all messages displayed on screen are marked as read. If you mark-unread a message then for how long would this mark remain? Would the message remain unread if looking at the message/chat another time? If so how would you get rid of unread-state? These complications are probably why no messenger has "just" implemented mark-unread.
@delta @eighthave as mentioned in the other subthread, Slack does this. It remains unread until that chat/thread is entered again. There are some quirks to it. Sometimes things seem to stay "unread" when they shouldn't or return to "read" when they shouldn't, but on the whole it's not a terrible UX. Handling edge cases may be tricky, but its achievable.
@eighthave That's a big part of my workflow too, the only one I know of that does that (also let's you snooze messages to alert you later) is slack. Really need that in Signal & Element. I don't know Delta though, does it have this? what a strange idea