4 ms·

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

by css 5y ago

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-conversations.html https://docs.mattermost.com/messaging/organizing-conversatio...

renewiltord 5y ago
That looks identical to Slack's implementation to my eyes. If you don't mind sharing, what did you like better?
- css 5y ago
  Slack threads don’t (or at least, didn’t; it’s been a couple years) show in the main message feed, they show when you expand the thread into the sidebar. In the feed, it shows the original message with an “n replies” text below it. 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.
  - renewiltord 5y ago
    Ah interesting. I believe Slack does the former thing (displays as k replies) but not the latter. Thanks.
  - jjjgcddf 5y ago
    You might not have noticed but your link goes to the new design (in beta) of collapsed threads which are much more similar to Slack's and I think this has caused some confusion in this thread It's worth noting that the design you prefer isn't being deprecated; Slack-style threads are being added as a user display option.
    - css 5y ago
      Oops, yeah. Looks like there are not really any docs for the existing (better) system: https://docs.mattermost.com/messaging/sending-receiving-messages.html#reply-to-messages https://docs.mattermost.com/messaging/sending-receiving-mess...
  - qudat 5y ago
    Slack has the option to "reply in main channel" as well as have it show up in the thread. This allows people to surface something important in the thread that should also be in the parent channel.
jks 5y ago
I have liked Zulip's threads (they call them "topics") best: https://zulip.com/help/about-streams-and-topics https://zulip.com/help/about-streams-and-topics
- nerdponx 5y ago
  I always found Zulip too thread-focused. I think the Slack implementation is a nice balance.
  - maccam94 5y ago
    In Zulip you can make a "general" topic thread, and then move messages to a new topic when you feel like it's warranted. The normal stream (channel) view shows all threads simultaneously. There's also a view of all streams combined. The UI would be more confusing if Zulip had to display un-threaded messages, because then you wouldn't have a way to view only un-threaded messages without threads being interspersed. If you use the "general" topic method you can just focus on that.

by css 5y ago

renewiltord 5y ago

That looks identical to Slack's implementation to my eyes. If you don't mind sharing, what did you like better?

css 5y ago
Slack threads don’t (or at least, didn’t; it’s been a couple years) show in the main message feed, they show when you expand the thread into the sidebar. In the feed, it shows the original message with an “n replies” text below it. 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.
- renewiltord 5y ago
  Ah interesting. I believe Slack does the former thing (displays as k replies) but not the latter. Thanks.
- jjjgcddf 5y ago
  You might not have noticed but your link goes to the new design (in beta) of collapsed threads which are much more similar to Slack's and I think this has caused some confusion in this thread It's worth noting that the design you prefer isn't being deprecated; Slack-style threads are being added as a user display option.
  - css 5y ago
    Oops, yeah. Looks like there are not really any docs for the existing (better) system: https://docs.mattermost.com/messaging/sending-receiving-messages.html#reply-to-messages https://docs.mattermost.com/messaging/sending-receiving-mess...
- qudat 5y ago
  Slack has the option to "reply in main channel" as well as have it show up in the thread. This allows people to surface something important in the thread that should also be in the parent channel.

jks 5y ago

I have liked Zulip's threads (they call them "topics") best: https://zulip.com/help/about-streams-and-topics https://zulip.com/help/about-streams-and-topics

nerdponx 5y ago
I always found Zulip too thread-focused. I think the Slack implementation is a nice balance.
- maccam94 5y ago
  In Zulip you can make a "general" topic thread, and then move messages to a new topic when you feel like it's warranted. The normal stream (channel) view shows all threads simultaneously. There's also a view of all streams combined. The UI would be more confusing if Zulip had to display un-threaded messages, because then you wouldn't have a way to view only un-threaded messages without threads being interspersed. If you use the "general" topic method you can just focus on that.