Introducing Threads in Beta

Post by alanfranz » Sat, Apr 23, 2022, 2:14 PM UTC

kadoban wrote: post #5

alanfranz wrote: post #2

I think threading in chat apps is a terrible idea. It’s a way to merge email and chat, but chat apps like Slack aren’t really suited for such replacement imho. Why threading if there’s not much noise? And if the noise is too much, maybe a public chat is not the best idea. on Slack, navigating a channel between “main” messages and thread messages is a nightmare, and since “main” messages are not just a subject, you sp…

I don't really see the issue with it. In Slack, we have a channel for our team. In that channel we have conversations, often more than one at a time, spread out over minutes to days. Why shouldn't each conversation have its own separate thread? The only real problem(s) I have with threads in Slack are: 1. some people suck at remembering to reply in thread. This isn't too serious though, once there's more than 2 messa…

Post by alanfranz » Sat, Apr 23, 2022, 2:16 PM UTC

viccuad wrote: post #17

alanfranz wrote: post #2

I think threading in chat apps is a terrible idea. It’s a way to merge email and chat, but chat apps like Slack aren’t really suited for such replacement imho. Why threading if there’s not much noise? And if the noise is too much, maybe a public chat is not the best idea. on Slack, navigating a channel between “main” messages and thread messages is a nightmare, and since “main” messages are not just a subject, you sp…

The underlying issue to me is the different velocity of different conversations between the same people in a room. Conversation 1 can be fast, with short messages and informal, Conversation 2 can be slow, with long technical messages or attached files. And all in between. Sometimes one type of convo transforms into another. And the tool should reframe it so: either by providing a schism for a new thread, changing the…

Post by [deleted] » Sat, Apr 23, 2022, 2:21 PM UTC

barnabee wrote: post #7

dmitriid wrote: post #3

None of these "innovative chats" that already use a browser to display them can even come up with the idea of tabs . Nope, they all insist on keeping everything inside a single window. So even if you have thread "for better communication with no noise", it still gets lost in all other threads, and they come up with workarounds like a dedicated page for threads etc. Just give me tabs, damnit.

Absolutely. I miss having multiple windows, each with one or more tabs, all respectful of my screen real estate! With most IRC clients or multi protocol chat programs you could have a couple of important channels always visible on a second monitor, key people you DM a lot in a tabbed window somewhere prominent, active chats open next to your work, and everything else in the main app window, minimised. Now we have a w…

Post by jdright » Sat, Apr 23, 2022, 2:27 PM UTC

replygirl wrote: post #43

sandstrom wrote: post #28

What I'd prefer is the Twist-style threads (Zulip may also have them), where every room/channel must contain only topics/threads, and those topics have a title/description, and any messages in them are 1-level (no nested threading). It looks like this: #office [room/channel] * Lunch [thread/topic] - Anyone wants to grab lunch today? [message] - Sure, I'll join! [message] - Me too! [message] * Printer doesn't work [th…

you can enforce this in slack with a toggle

Post by lijogdfljk » Sat, Apr 23, 2022, 2:29 PM UTC