Why is the use of slack threads discouraged? It se...
# squarelibraries
t
Why is the use of slack threads discouraged? It seems like everyone is ignoring that anyway
plus1 1
e
If anything it should be encouraged mandated. Threads keep discussions together, so they don’t overlap and you can skip the whole thing if it does not interest you.
💯 3
t
something about information silo and shitty search behavior iirc. not sure if still true. I think it is a jake-ism
2
j
This is a chat room, not a forum or support group. Slack is such an awful tool for communities like this. Truly the worst of a chat room and a proper threaded system (like Zulip or even full on Discourse) combined.
An interesting thread that's offscreen is visible to no one except those involved. People are not scrolling up to find "active" threads. How would you even know? Mentally keeping track of reply counts of all 62,361 threads in this channel's entire history of existence?
I agree threads should be mandated, on a platform which actually honors threads as a first-class citizen and not this bolt-on bullshit Slack peddles. They added threads in the laziest way possible and it's a complete shit show.
By mandating threads you actually remove the utility of threads because it's impossible to thread within a thread. We're forced to do things like quote reply to ask follow-up questions to something higher-up because I have no way to actually responding directly to something that isn't extremely recent within a thread.
t
Suddenly reddit comment trees make sense 😂
👌 1
j
If my window was like 14px shorter I would never have even seen this thread. Are people talking in threads higher up? Who knows! Slack does absolutely nothing to draw attention to active threads vs. inactive ones and instead gives us whatever this all is.
😄 1
👍 2
Threads in a channel should be able to be disabled. Replies to older messages would then work like clicking the "post reply to channel" box only. However, if they are enabled, then creating a new thread should be harder than simply typing into the chat box (like a "create new conversation topic" button and then a popup message box and a "create" button). Those should then be sorted by activity like a forum. And whether you're subscribed to each conversation or not should be visually indicated.
t
I’d argue this channel very much is for support.
plus one 1
j
Well then we should shut it down because Slack is a dogshit support product
Getting help and being provided support are not the same thing
t
That’s a strange hair to try splitting. I think there are levels to support, of which getting help is one.
plus one 1
But if you don’t want me to provide support here I can respect that. It is your channel
j
If I wanted to provide support I would use a tool that was built to actually facilitate that. Not a chat product with trash threads.
We provide quite a lot of support on GitHub issues, GitHub discussions, and StackOverflow. These places facilitate asynchronous communication and knowledge sharing, they provide statuses as to the resolution, they are searchable and in a well-known locations associated with the projects.
☝️ 1
This place is a random assortment of people answering a few questions or responding to feedback on whims.
It is a fundamentally a chat room with tiny information silos. If two people want to have a chat in a thread that's four pages scrolled offscreen and come to the wrong conclusions about a problem, the motivations behind something, or the path going forward with a project then they are free to. Chances are no one will see it and correct them. Or maybe thousands will see it in search because Slack search can't rank things because every message has the same weight.
t
I’ve clearly hit a sore spot, and I’m sorry. Message received.
j
It's not a sore spot at all, really, unless you're a Slack PM. You asked a question about something on which I have a strong and fairly-well informed opinion on. I am not basing this on a whim, but experience and empirical evidence based on this room and other rooms in this and other Slacks. Other channels thread everything and you get really high-quality questions with high-quality answers with high-value participants with active discussion lost in a sea of low-value questions with low-value answers that have been asked 50 times in that room over the last year. This room becoming like the #compose channel would be very sad and a failure. It wastes the resource that is access to all of these people that works on the projects that this room covers.
👆 3
e
Lots of good points, but disabling threading only makes it worse. It means I won’t use this channel except to solve my own problems because it’s too noisy. I will feel less motivated to give back. I am working on a product that will fix all of these problems, if all goes well.
j
It doesn't really make it worse, because it forces you to split the channel when its scope gets too large. Or to simply use a better tool.
There's many decades of IRC which have proved this model to work reasonably well
e
What is this better tool I can use now; stackoverflow?
IRC was a bad product, which is why it died.
j
I think you've missed my point
e
The problem is not the scope of the channel; it’s that everything is bleeding into everything else. It is noisy. And that repels people who value their time. The kind of people you’d want in a knowledge community. Someone not interested in the threading debate would be totally wasting their time reading this one. They probably want to know about Square libraries, not this meta discussion. But it would be in their face if we did not use threading.
j
Please stop editing your posts
e
Why???
j
Because I'm not going to read them 8 times to diff what was added
e
You’re not the only person who’s going to read them.
I am not optimizing for you.
j
You are not optimizing the person who is present in the chat?
e
If I wanted to have a chat with you, I would send you a private message. This is a public discussion.
I think you are confused about what this product is.
j
You are entitled to your opinion. Bye!
c
i will add that i do like how this room is more like a chat/irc. miss those days
m
While I agree with the problems Jake mentions, I do find the “get notified about new replies” context menu option on messages very useful. I browse lots of channels on this Slack and when someone posts an interesting question I can “subscribe” to it and get notified if someone replies. Without threads I would be unable to subscribe to a conversation.
👍 1