> like the threaded messaging, kind of a mess, maybe we just don't do it right I haven't found any chat style application that does threaded messaging "right"

> like the threaded messaging, kind of a mess, maybe we just don't do it right I haven't found any chat style application that does threaded messaging "right" with how I think it should work (I want real time USNET with thread level ACLs). That said, they're all ok IF (and that's a big if) everyone working with the accepts the "this is how they work" and use it as such with the appropriate level of technical literacy (and that's a big part of the big if). Slack is ok. Its one deep and for active channels it can solve the "get a thread you two" so that a conversation doesn't spill over into the main channel. However, that hurts discoverability of messages... and for less active channels is likely overkill. Zulip's is better than Slack with its topics... but is way overkill for a bunch of friends. Teams has two styles with the team "here's a post, followups go on that" and "here's a group chat" which has no threading at all and tend to have new group chats forked for each new topic. Discord has threads which allow for the slack style "get a thread" and a bit more ACL on the thread (different permissioning model for the base application). All that said, I believe that the real thing that is lacking isn't threaded conversations but a strong chained reply-to feature. The best example of this I can find is Stack Overflow chat. For example, https://chat.stackoverflow.com/transcript/message/55971002#55971002 https://chat.stackoverflow.com/transcript/message/55971002#5... which is a reply (you can see that arrow thing) that you can click on and then follow to the message that it was a reply of, which itself is a reply to another comment. And so, for me, it's not the thread that is important as that is discoverable - but rather the "what is this replying to?" along with the ability to fork a new room/channel that handles a given topic (because everything in one room is a complete mess). Returning back to teams... it's ok. It serves the simplest interface acceptably. Every chat app would work better if everyone used it to its fullest... but as long as there's someone who doesn't use it "right" I'm going to suggest that Teams or Discord are probably the easiest to not use wrong (or set up to limit the 'how it can be used wrong is difficult').