21–30 of 233 posts
Sadness. I use Google Chat at work and I absolutely hate threads there. Maybe the Discord implementation is better, but I'm not holding my breath.
I like the idea of having temporary side conversations with a time limit. There should never be an "eternal" thread, just things that come and go.
Is there really no better design for "aside" conversations than this? People lean on Slack threads too much, leading to a confused flow of conversation that makes it extremely difficult to piece together how the discussion was ended or resolved.
Earlier quoted context omitted.
I’m always surprised by how practically every single opinion regarding personal communication is the opposite in hacker news to the mainstream opinion of my “real life” circles. Use of social networks, slack, emojis, messaging apps, sync vs async communication… Its not a criticism of any kind, mind you, it’s just very surprising to me.
I would be a bit slower on the hasty generalizations. I’m here on hacker news and I love using threads and am happy they’re coming to Discord there’s also multiple comments below this saying the same thing.
There was simply no way to know who someone is replying to, or part of which of the multiple conversations in the channel is that message a part of
Earlier quoted context omitted.
Of all the chat apps I have used, Mattermost's implementation of threads/replies [0] has felt the most natural. That said, all implementations I've tried leave something to be desired. [0]: https://docs.mattermost.com/messaging/organizing-conversatio...
That looks identical to Slack's implementation to my eyes. If you don't mind sharing, what did you like better?
In Mattermost, new replies show as normal messages in your feed with a bit of context for what they’re replying to, and clicking on the context expands the full thread in a sidebar.
I find the Mattermost implementation more ergonomic because you can read replies without expanding the whole thread every time, and stale threads will get bumped by new messages.
Is there really no better design for "aside" conversations than this? People lean on Slack threads too much, leading to a confused flow of conversation that makes it extremely difficult to piece together how the discussion was ended or resolved.
Of all the chat apps I have used, Mattermost's implementation of threads/replies [0] has felt the most natural. That said, all implementations I've tried leave something to be desired. [0]: https://docs.mattermost.com/messaging/organizing-conversatio...
Far far better than other abominations like slack - which hides streams of conversation behind a wall, making the UX terrible.
The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
Earlier quoted context omitted.
Of all the chat apps I have used, Mattermost's implementation of threads/replies [0] has felt the most natural. That said, all implementations I've tried leave something to be desired. [0]: https://docs.mattermost.com/messaging/organizing-conversatio...
I have liked Zulip's threads (they call them "topics") best: https://zulip.com/help/about-streams-and-topics