A channel gets noisy pretty fast if people don't use threads. People start answering something that was way back on the chat. There is a rule of thumb on a friend's of mine company where every new TOPIC should be in a thread. Otherwise, when you're gonna try to catch up everything that was discussed after a while there is only noisy and you have to read everything from the start even if you don't care on the discussed TOPIC. So, after a while you start ignoring all messages and mark the channel as read and go on with your life.
- Important messages are easily lost. I don't know to fix this other than better organizational discipline, but it'd be great if this was solved in the app instead of trying to convince 200+ employees (at my current gig) of the "right" way to use a chat app.
I hate that they are now trying to force me to use their app instead of the browser. I log in and they throw up a bullshit delay while they “reticulate the splines” and other bogus crap followed by “click here to open in the browser”-—it’s a deliberate waste of time specifically designed to piss me off enough to give in and install the app. Obstinate person I am, this only strengthens my resolve.
Also, slack absolutely sucks at providing a useful repository of previously answered questions. It is only useful for ephemeral chitchat.
Thread implementation is not great:
- can’t share a message in a thread with the thread
- notification of a new message in a thread in a channel should be on by default
- @mentions in threads should notify in channel where thread lives and in “Threads” thing
What do you mean with "Threading should be default or easier to access"?
I personally hate that interesting conversations may happen in threads that I'm not following, I developed the habit of clicking "Follow message" on almost every message just in case a thread develops around that message.
