131–140 of 233 posts
It's fine, not every product needs to be super original I guess, but it's gotten to the point where choosing one over the other is barely even a statement about your identity anymore. Although I guess most people do both: Slack for work, Discord for friends. It's boring when those two experiences are so similar, tho
Fun fact: They granted create threads to everybody by default but granted manage threads to nobody by default. So we had moderators who could delete channels, delete create and modify roles and role permissions, and delete messages as well as ban/kick users, but couldn't manage or delete threads. "public threads" show up in the main channel list to everybody as a sub channel, and everybody had permission to create an…
This happened to me, moderating a server, while our only admin was on vacation. I was able to remove "create thread" permissions from the default role, effectively turning threads off. But first I had to add a new role to grant myself those permissions. I also had to ask people who had created threads to please delete them because I still can't.
Assuming you're an Administrator, it's covered by that.
It's disappointing that it's so hard to convince the companies "management" to switch from chaotic Slack communication to something better for async and organised communication because clients are used to Slack...
The same applies to Discord as it's just the most accessible way, everyone uses and it's just largest common denominator regardless of the chaos in most of the channels, hope the threads will clear some things up when people use them, and not like in the Slack where everyone just paste response in the channel instead of the threads.
Earlier quoted context omitted.
I have liked Zulip's threads (they call them "topics") best: https://zulip.com/help/about-streams-and-topics
I always found Zulip too thread-focused. I think the Slack implementation is a nice balance.
The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
I understand the "also send as direct message/to group" mimics this. This, for me, is a good thread implementation for a chat tool.
Earlier quoted context omitted.
They've given that choice to servers that are labeled "Community Servers" at least (giving them until mid-August before it is forced on by default) which will help some of the largest servers, but yes they maybe should have given that a wider option to the medium/smaller servers too.
Yep, we're a small server (~2700) that just randomly had it turned on. We've currently got about 10, just from random members thinking to test if they can create them. 10 that we can't delete. Thankfully nobody has tried to abuse it by naming any anything offensive, or mass creating them yet. Hopefully they won't before the admin gets back on when he wakes up.
The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
Earlier quoted context omitted.
I work at Mattermost -- we do have this, it's just still in beta right now https://docs.mattermost.com/messaging/organizing-conversatio...
Does Mattermost also have "uncollapsed" threads like Flowdock? Personally, I think hiding conversation in a group channel is terrible UX. I don't know why people are aping Slack's functionality when I hear almost universally that it sucks.
The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
I'm not sure if this is appropriate, but getting conversation representation and message sorting right is the largest focus of my passion project, Ametha.
It would be amazing if I could have a 15 minute voice call with you to hear about your experiences with online communication & collaboration?
The offer is obviously open to anyone else here as well, but no pressure at all, and apologies if HN is not the right avenue for this.
Edit: Feel free to use the email in my profile