3 ms·

We have 'replies' (which lets you post a message into the main timeline which refers to an existing message in the timeline), but we don't yet have 'threads' (w

We have 'replies' (which lets you post a message into the main timeline which refers to an existing message in the timeline), but we don't yet have 'threads' (which lets you branch the conversation into a sidebar). The protocol actually has support for label-based threading (i.e. "hide all messages tagged #gif" or "only show messages/conversations in this room tagged #work") already, as per https://github.com/matrix-org/matrix-doc/blob/matthew/msc2326/proposals/2326-label-based-filtering.md https://github.com/matrix-org/matrix-doc/blob/matthew/msc232.... But we haven't had a chance to hook this up into Riot yet, thanks to all the work spent on E2EE by default. Proper threads will come in time however.

godelski 7y ago
Thanks for the reply! Yes, threads. That's what I'm thinking of. I find these super useful. I know some people don't like them, but they can just not use them if that's their preferred style. I would really just like threading a comment rather than having to label everything. I'll be honest, I'll just get lazy and not label. I doubt I'm the only one too, or in the minority. > Proper threads will come in time however. Awesome, this was really the only thing that makes me hesitant to switch. I can stand an ugly UI if I can get good conversational flow.
0az 7y ago
Hot take: slack-style threads are bad for long-form discussion. They encourage forking, when what you really want is everyone to be on the same page. Traditional forum-style threads, or "channels" on a chat app, is optimal for discourse, as it encourages continuous convergence and integration rather than splintering. Hiding tangents serves to lower the quality of conversation. Optimal within the constraints of real time chat IMHO is slow-mode (5 to 15 seconds, or possibly greater) in a single channel.
- godelski 7y ago
  IME tangents, while possibly fruitful, just lead people to skip the 30+ messages and so doesn't become helpful. Hot take: make threading an option. If you don't want them, don't use them. If you want them, then they are available. This is clearly a personal difference with no right or wrong answer. So the solution is options.
the_duke 7y ago
I find Zulips threading/topics UI brilliant for certain kinds of channels and discussions. I hope that Riot will implement something similar, potentially as an individual or per-channel setting.

godelski 7y ago

Thanks for the reply! Yes, threads. That's what I'm thinking of. I find these super useful. I know some people don't like them, but they can just not use them if that's their preferred style. I would really just like threading a comment rather than having to label everything. I'll be honest, I'll just get lazy and not label. I doubt I'm the only one too, or in the minority. > Proper threads will come in time however. Awesome, this was really the only thing that makes me hesitant to switch. I can stand an ugly UI if I can get good conversational flow.

0az 7y ago

Hot take: slack-style threads are bad for long-form discussion. They encourage forking, when what you really want is everyone to be on the same page. Traditional forum-style threads, or "channels" on a chat app, is optimal for discourse, as it encourages continuous convergence and integration rather than splintering. Hiding tangents serves to lower the quality of conversation. Optimal within the constraints of real time chat IMHO is slow-mode (5 to 15 seconds, or possibly greater) in a single channel.

godelski 7y ago
IME tangents, while possibly fruitful, just lead people to skip the 30+ messages and so doesn't become helpful. Hot take: make threading an option. If you don't want them, don't use them. If you want them, then they are available. This is clearly a personal difference with no right or wrong answer. So the solution is options.

the_duke 7y ago

I find Zulips threading/topics UI brilliant for certain kinds of channels and discussions. I hope that Riot will implement something similar, potentially as an individual or per-channel setting.