Feature Description
Element implements MSC3440. It adds another hierarchical level to channels, where responses aren't inline in the main chat, but separate "sub-channels". People can create new threads and post messages to threads.
Rationale
This feature is excessively used in many of the larger channels I'm in. Fluffychat looks really enticing, but without that feature, all of the responses are within the same stream and so I don't know what the messages are a response to, and I also can't participate. This makes it impossible for me to use the client in practice.
Mockup
I can't really draw them out, but I can write out some text:
The way Element implements Threads is not so great, because they're hard to reach and easy to miss. I personally prefer the way Discord does them (which is identical from a features perspective). Luckily, they have a nice introduction here with animated gifs.
If there are any unread messages in a thread on a channel you haven't muted, these threads are added in the channel list as a lower level row (making it a tree view). Clicking on them directly opens up the thread (which looks identical to the regular channel view). The back arrow button on the top left moves back to the main channel.
If you want to look at a thread without unread messages, there's an action button on the top right within the channel to open up a side panel (or popup) listing all threads showing the last message plus a timestamp. Clicking on a row there opens the corresponding thread view (as above).
Additional Context
No response
Feature Description
Element implements MSC3440. It adds another hierarchical level to channels, where responses aren't inline in the main chat, but separate "sub-channels". People can create new threads and post messages to threads.
Rationale
This feature is excessively used in many of the larger channels I'm in. Fluffychat looks really enticing, but without that feature, all of the responses are within the same stream and so I don't know what the messages are a response to, and I also can't participate. This makes it impossible for me to use the client in practice.
Mockup
I can't really draw them out, but I can write out some text:
The way Element implements Threads is not so great, because they're hard to reach and easy to miss. I personally prefer the way Discord does them (which is identical from a features perspective). Luckily, they have a nice introduction here with animated gifs.
If there are any unread messages in a thread on a channel you haven't muted, these threads are added in the channel list as a lower level row (making it a tree view). Clicking on them directly opens up the thread (which looks identical to the regular channel view). The back arrow button on the top left moves back to the main channel.
If you want to look at a thread without unread messages, there's an action button on the top right within the channel to open up a side panel (or popup) listing all threads showing the last message plus a timestamp. Clicking on a row there opens the corresponding thread view (as above).
Additional Context
No response