4 ms·
Yea. The reply feature in Discord is way better and their introduction of "threads" makes everything worse.
by boxed 1y ago
Yea. The reply feature in Discord is way better and their introduction of "threads" makes everything worse.
- squigz 1y agoWhat happens in Mattermost if you open up a thread and send a message in it without replying to a message? Does it still show up outside of the thread? I can see how that might be confusing.
- pcthrowaway 1y agoIf you make the reply in the thread it will go in the thread. Threads in Mattermost are single-tiered (you can't do sub-threads). So they're somewhat limited, and sure, people will occasionally respond to thread conversations out-of-thread. That's a user issue more than anything else. They're not perfect, but they are very useful.
- squigz 1y agoYeah that makes sense. Still loads better than the way Discord does it currently.
- boxed 1y agoHmm, I don't remember it like that. Isn't that exactly how Discord and Slack does it?
- squigz 1y agoI've never used Mattermost, so I'm only going off my reading of what you said, but the difference is that, if you're not actually in a thread when you reply to a message on Discord, it doesn't get put into that thread, whereas on Mattermost, IIUC, you're saying that you can reply to a message outside of a thread and be able to click into a thread made of all those replies. My question (and pcthrowaway's) response is about what happens when you send a message inside a thread without replying to a message. I was wondering if it would be sent into the main channel, with no context, which would be confusing.
- boxed 1y agoFrom what I remember then it works exactly like if you pressed reply to the last message and sent it.
- pcthrowaway 1y agoIt sounds like you're under the impression that threads can only be started by "replying to a message". That's true in the sense that threads are created when you hit the reply icon to a top-level message, and type a response in the section for the thread starting with that message. Afterwards, all responses sent in the thread are part of that thread. By default, on versions of Mattermost in the last year, these are visually separated from the channel, almost like a sub-channel that you can reply in. In the web app, the thread is off to the side of the main channel. Responses in the thread do not show up on the channel; the top-level messages which have replies in-thread say the number of messages in that thread, which you can click on to open the thread. Messages sent to the main channel go to the main channel, but in the thread view, you're not necessarily replying to any one specific message, just posting a message in the thread. I think there are other ways to view this though, so based on user settings it may also be possible to see threaded responses in the main channel (I haven't experimented with the alternate view settings though) Not sure if that answers your question, but you can always join the mattermost official server and try it out yourself if you're curious: https://community.mattermost.com/ https://community.mattermost.com/
- squigz 1y ago> It sounds like you're under the impression that threads can only be started by "replying to a message". That's true in the sense that threads are created when you hit the reply icon to a top-level message, and type a response in the section for the thread starting with that message. No, I'm just focusing on reply-chains and their interactions with threads because the former often leads to the latter, and I misunderstood the original comment. This clarifies things though and is indeed exactly how Discord does it. I just wish there was a better way of handling threads - it seems to me that it's too easy for a conversation to be shoved into a thread and then be forgotten if you're not actively looking for it. That's fine in some cases, like work discussions, but not for say a social community. Thanks for the responses!