On IRC you just take the discussion to another channel, which can be created ad-hoc and trivially disposed of when no longer necessary. Or you just become good at reading around multiple conversations at once. There's also no expectation that you need to read everything to catch up when you come back after a while - take that to email if you need to. Much better real time chat culture, imo.
To be fair, that same trivial disposed chat concept you mentioned lives in Slack, as well. It's incredibly easy to quickly make a group DM chat from a channel. > "There's also no expectation that you need to read everything to catch up when you come back after a while - take that to email if you need to." Slack doesn't require that expectation, either. You can easily change settings of Slack to just ignore messages t…
Threaded messaging comes to Slack
11–20 of 96 posts
Re: Threaded messaging comes to Slack
#12I'm actually a bit sad about this. To me the whole thread thing is the biggest issue with Microsoft Teams. In my opinion it really makes the channel hard to read and keep track of. I like the first part of the Slack implementation where the thread opens up in a new pane on the right but where it falls apart (for me) is how it displays in the main channel.
You don't want EVERYTHING to be a thread, but sometimes - rarely, you do want something to be a thread for the sake of the flow of the particular channel.
Re: Threaded messaging comes to Slack
#13I've spent a lot of time thinking about the problem of how to make threading work as the lead developer of Zulip, an open source group chat application where every conversation is threaded, and I think adding Facebook-style comment threads to messages is the wrong approach. Fundamentally, what you want is to be able to read and participate in multiple conversations with a given group of people (a channel) at the same…
Your comment seemed pretty genuine, until you had the 3 paragraph plug for your Zulip product that competes with Slack.
It's hard to talk about Slack's threading solution without also talking about what I think is the best way to solve that problem.
Re: Threaded messaging comes to Slack
#14Earlier quoted context omitted.
To be fair, that same trivial disposed chat concept you mentioned lives in Slack, as well. It's incredibly easy to quickly make a group DM chat from a channel. > "There's also no expectation that you need to read everything to catch up when you come back after a while - take that to email if you need to." Slack doesn't require that expectation, either. You can easily change settings of Slack to just ignore messages t…
I'm not saying Slack doesn't have the features to support this. I think that the addition of threads are a response to a lack of this culture.
Re: Threaded messaging comes to Slack
#15I've spent a lot of time thinking about the problem of how to make threading work as the lead developer of Zulip, an open source group chat application where every conversation is threaded, and I think adding Facebook-style comment threads to messages is the wrong approach. Fundamentally, what you want is to be able to read and participate in multiple conversations with a given group of people (a channel) at the same…
Re: Threaded messaging comes to Slack
#16I've spent a lot of time thinking about the problem of how to make threading work as the lead developer of Zulip, an open source group chat application where every conversation is threaded, and I think adding Facebook-style comment threads to messages is the wrong approach. Fundamentally, what you want is to be able to read and participate in multiple conversations with a given group of people (a channel) at the same…
I work at Stack Overflow, where our company chat is split between Slack and an internal chat product we made ourselves years ago.
I think the "comments as threads" concept helps solve some specific use cases (like room clutter) but not the use cases I personally care about the most.
The "in-line method" mentioned in this other article about the change is my preferred method: https://www.fastcompany.com/3067246/innovation-agents/the-un...
My gripe doesn't stem from rooms being too cluttered, it stems from if there are 4 people talking at once and I'm in two different conversations chains with them, I'd like to explicitly reply to a specific message and carry on the convo. not hide it in a comment thread.
On our homebuilt chat product this is the difference between starting a message with `@Name` or hitting "reply" on a specific message and having `@:{Message Id}` as the beginning of your message.
It shows the same to the users, they seen `@Name`, but if it's a specific message reply when they hover over the message the one it's in response to gets highlighted (and there's a button to scroll to it if it's off-screen).
I think this Slack feature, like most features, is targeted at helping people using chat sitting in the same room or office together.
I work at a very remote company where with some people I share less than 2 hours of a work day. I want better chat tools centered around making our async communication flow better. Not out-of-room comment threads.
Re: Threaded messaging comes to Slack
#17I've spent a lot of time thinking about the problem of how to make threading work as the lead developer of Zulip, an open source group chat application where every conversation is threaded, and I think adding Facebook-style comment threads to messages is the wrong approach. Fundamentally, what you want is to be able to read and participate in multiple conversations with a given group of people (a channel) at the same…
Your comment seemed pretty genuine, until you had the 3 paragraph plug for your Zulip product that competes with Slack.
Re: Threaded messaging comes to Slack
#18Re: Threaded messaging comes to Slack
#19I worry that they're gonna start messing with what made them special in the first place.
Re: Threaded messaging comes to Slack
#20I've spent a lot of time thinking about the problem of how to make threading work as the lead developer of Zulip, an open source group chat application where every conversation is threaded, and I think adding Facebook-style comment threads to messages is the wrong approach. Fundamentally, what you want is to be able to read and participate in multiple conversations with a given group of people (a channel) at the same…
iOS client not avail in US?
The development community has been rewriting the iOS app in React Native over the last couple months, and the new version is working really well! It'll be in the app store in a few weeks. See https://github.com/zulip/zulip-mobile.