-
Notifications
You must be signed in to change notification settings - Fork 98
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
Inability to distinguish between replies & threads (which could be a very easy fix) #1333
Comments
UI proposal: prefix the sender of the reply-preview message with 🧵 if the reply is part of a thread, until we have proper thread UI |
Is this true? I've been using replies as a 'hack' on EX to reply in threads and at least a few weeks ago that was working great. |
If you hit reply to the message, it's fine. The problem is that you don't know whether to hit reply or not, because you don't know if it's a thread, hence this bug. |
Aha gotcha (I'd misread point 3!). |
Another thought: i wonder if we easily do very simple poor man's threading like iMessage does - i.e. hide messages from the timeline which aren't part of the thread if the user views a message. We could do this locally without having to use any server-side or even rust-sdk threading APIs as a first cut? (i.e. literally iterate over the timeline and hide the messages which aren't in the thread?) |
@stefanceriu @bmarty would this be easy to do? To 1) distinguish between threads and replies 2) to visually differentiate between the two without building the whole threads feature on EX 3) will this influence how notifications function on EX in any way? |
|
This was fixed by #1686 in 1.2.9, wasn't it? |
Steps to reproduce
In other words: EX currently acts as a non-thread-aware client currently, showing threads as replies. Proper thread support is a while off.
However, if app showed you which replies were actually threads (and which were instead boring old replies), then the user would be able to much more effectively participate in threads - by knowing when they'd need to hit reply to participate in the thread, rather than talking normally in the room and fragmenting the thread for folks on thread-aware clients.
Outcome
What did you expect?
EX should tell me somehow which replies are actually threads, versus plain replies in the main timeline.
What happened instead?
EX doesn't, so as a user you don't know if you need to send an explicit reply in order to keep your message in the right place in the thread, or whether you can just send a normal non-reply message.
Your phone model
No response
Operating system version
No response
Application version
292
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: