3 ms·
> And at this point, Slack’s method of creating a separate thread in response to any message is by far the most effective, but feels clunky within the interface
by antihero 6y ago
> And at this point, Slack’s method of creating a separate thread in response to any message is by far the most effective, but feels clunky within the interface, as if it were an afterthought.
I disagree hugely. At least for casual messaging, they're far too heavyweight for 99% of situations that are perfectly well suited to comment replies. Our brains are fine at picking out the context.
For casual chat, you don't want to overstructure things. Also with threads now you have to have some way of managing previous contexts (do you need to scroll up to find/reply to threads? Is there some sort of weird thread view?)
- spurgu 6y agoAgreed that Slack's "main" thread view sucks and I only use the sidebar view, it's really difficult/cumbersome to move between threads. I think some kind of tabbed interface could work. And I'm all for threaded conversations, something evolved from Slack's model. Purely linear is so damn noisy and participants are forced to follow a lot of uninteresting shit that could've gone on in a thread instead. This happens a lot even with chats with small groups of friends.
- jacobolus 6y agoSlack and its threading model is one of the most frustrating communication tools I have ever used. Zulip is unimaginably better for long-running semi-structured conversations, both for casual lurkers and heavy participants.
- spurgu 6y agoYeah I've only tested Zulip briefly but it seemed like just that, Slack threads evolved. At first I was put off by everything showing in the main view, until I realized I could filter everything.
- lmm 6y agoYeah, I think what Discord does here is a lot better - you can mark a message as a reply to a previous message, but it stays in the main conversation rather than forking off as a separate thread.