I think the too-many-channels problem is a symptom of the excessive walled gardening.
Slack segregates by interests and social group, and bundles that with strict gatekeeping. There is no way for people to remix that to suit their own preferences. You can only fragment existing communities more.
I would love a slack multiclient where I can put channels I care about side by side, regardless of origin, and keep the rest out of sight. Instead now everyone has their own #random and #offtopic and so on. Cruising between Slacks and Discords is like navigating a hall of mirrors. If there is disagreement, the only solution is complete schism.
Re:Slack's bait and switch
by pavel_lishin on Monday March 12, 2018 @08:51AM
(#16567801)
Slack's use as a "community" chatbox is a mangling of its original intent to be used by teams. That's where your pain points are coming from, and some of my own (no /ignore feature, for instance).
I have some of the same issues, but I'm not part of any community slacks. I run my own consulting company, and as such, I've been invited to most of my client's slacks. So I've currently got 37 Slack workspaces going. But most of the time, I'm only concerned with the specific project channel that I'm working on for a client, and I might only be active in 2-3 projects at a time. So I'd love, like OP, to be able to just have those 3 channels front and center.
Re:Slack's bait and switch
by pavel_lishin on Monday March 12, 2018 @10:35AM
(#16568360)
That's definitely a use case I hadn't considered.
When you already have too many channels, and then they give you the ability to have too many threads.
I feel like they do a worse job at the supposed value add of being able to archive and later refer to a topic of conversation than channels simply because they are so light weight and proliferate so many of them, potentially.
Plus it's really jarring to be pulled into a bunch of threads.