[notreallyserio]

> To me, it is incredible that Slack is used WITHOUT threads.

The first time information you need is sent in a thread that started a week ago and that you're not already on, you'll get why folks don't like Slack threads. They're an anti-feature, IMO.

If Slack offered a way to show all messages whether or not they're in a thread, as they come in, I'd be down. I wouldn't like 'em but at least I could work around their fundamental flaws.

[ydant]

And it's such a simple option to add, too - as far as I can tell, each message in a thread is just a message in the channel, just with a "threadId" attached to it. The client's the one that hides it and makes a mess of the experience.

But what it really needs is elevating threads to something like a temporary "sub-channel". Show them on the side-bar just like channels so you don't lose messsages CONSTANTLY if you're in more than 1 active thread at a time.

[hackandtrip]

I understand and agree on this, BUT I feel like we are not at the point where Slack could decide autonomously which threads deserve their own channel.

Usually, in our workspace, it's the person leading the discussion that at some points decide to redirect the talk somewhere else

[ydant]

I just dream of the day when Slack has "all threads with unread messages" show up in the side bar - somewhere. Let it be an option you can turn on/off, if need be. But right now I feel like I have to obsessively scroll down the threads list and look for things that are new.

Maybe it's a company size thing, as mentioned elsewhere in this discussion. At my size company (<10 people), every thread I'm watching - I pretty much need to see all of the new messages.

[rossmmurray]

Isn't this what the slack search bar is for? I was sceptical of using it at first but I often find what I'm looking for by typing in one or two key words and restricting the search to certain channels that likely have the information.

[notreallyserio]

Search can help address this issue if you know that people were discussing something you're interested in. However, it's possible (and in my experience likely) for an important topic to come up in a thread and not make its way back to the channel. In that case you may not know that it's something you need to search for.

[sstangl]

> If Slack offered a way to show all messages whether or not they're in a thread, as they come in, I'd be down.

This is how Zulip works. It's extremely effective.

[hackandtrip]

Well, that's because threads are just first citizen in Zulip, even more than in Slack!

Basically, a thread is visible at a first glance from the UI, while that's not true in Slack. Also, you can kinda replicate Zulip structure by just using channels with naming conventions, so you have: - generic channels, e.g. for status update for many stakeholders - specific channels for each feature - threads in each channel where you discuss a single point

[bgoated]

I second this. Zulip works extremely well at my workplace.