Hacker News Reader

Comment by nature | Hacker News Reader

There is an existing discussion to add threading to Element: https://github.com/vector-im/riot-web/issues/2349. To sum up, the backend already somewhat supports it by tagging a message with a `thread_id`. Then the UI can group messages by their `thread_id`s.

View on HN

Matrix already supports Zulip style threading via MSC2326 (https://github.com/matrix-org/matrix-doc/blob/matthew/msc232...). We haven't hooked it up in Element yet though (and ideally would do much better UI).

I'm curious about the priorization of this feature. In my personal experience (7 slack groups), the majority of the channels use threads. It's a very important feature to avoid drowning people in a stream of messages irrelevant to them.

I may be mistaken, but it doesn't look hard to add it to the UI if the back already supports it. Is the feature planned for a precise date ? Does the Element team lack money ? Can we pay for this feature, instead of paying Slack e.g. 30 000€/year ? Is the lack of developers the problem ?

Suggestion: offer multiple threads in the same window at once, since slack only offers 1 thread view at a time. IE where slack offers 1 sidebar for threads in 1 column, offer up to 6 threads in a window via 2 columns and up to 3 threads per column.

What it look busy when fully used? Yes, but sometimes when you are working in an Enterprise environment, you need to follow something across multiple rooms or channels and this would save users a lot of clicking back and forth.

while I'm sure there are oodles of feature requests already going, this would be one that would offer a genuine feature that slack does not.

The ability to open a separate tab or window for each thread is what I'd like. Really anything would be an improvement over a single, fixed-width column for a thread.

Reply on news.ycombinator.com