I have tried slack for some months and found it super laggy, both on the desktop and on android.
Then someone invited me to try Discord for company comms and I said "that's a gaming-oriented app, cmon it won't work well".... my mind was blown by how smooth Discord is.
We are a small shop but since we migrated from Slack to Discord we haven't been focusing much on 'how to communicate' but more on actually just chatting.
I advise everyone that talks about Slack to try Discord as a good alternative, even if your use case is synchronizing a loosely-knit team over the internet.
Hmm, looks like Discord backend is built on C++/Elixir/Erlang[1], and Slack is built on a scripting language. I think people underestimate the difference in scalability and UX with something like this that handles lots of small packets.
Discord's role/permission management is incredibly powerful. There's a couple things I'd love to see to make it a bit easier to use (duplicating/copying permissions between roles would be great), but I'm comfortably using it for a public Discord channel with 300+ members and growing[1] and I can actually visualize how to keep the chat functional if the member count grows by 10x.
I strongly recommend Discord over Slack for public chat groups; I'd happily use it over Slack for company chat as well, with the caveat that the integration/app story isn't quite as far along as Slack is.
I run a 3000+ person community on Discord. It's incredibly easy to get a simple access control list going which makes managing this many people a breeze. For public facing roles, users themselves can enter the Discord server and choose their own roles, which makes all my previously manual human tasks automated.
Clicking on a Discord message notification on the mobile app doesn't redirect you to the relevant chat, it just opens Discord at your last location. On the Linux desktop app there used to be many times it would get stuck on the loading spinner. It just feels less polished than Slack.
> If you write [here's a link](https://gmc.uy), it shows it as a link :)
> The nice part? it shows it as a link for everybody, not only those who have the extension installed.
Wait, wat? I'm looking at the code[0], and this is the most surprising part of this entire project to me. Slack goes out of its way to say "we don't support Markdown because we think the link support is an exploit." But they just have an alternate, undocumented way to send links anyway?
Is that a bug on Slack's side? I'm trying the syntax format that you're casting to in DMs to myself, and it doesn't seem to work? Are they doing clientside escaping or something?
Don't get me wrong, I think the "people might phish links" excuse is kind of lame when there are multiple ways for them to mitigate that problem, I'm just very curious about how and why this works.
I guess that if they consider it a vulnerability, they're going to do the check on the server side... I really hope they don't though.
If they do, I'll fix it on the extension (so only people with the extension would see the markdown links as real links).
Also: to answer your question... yes, there's an undocumented way of sending them. And yes, the client escapes `<https://url.com|the title>` to `<https://url.com|the title>`.
The format is the same format used by bots to generate links.
I don't think it's a bug, since they've always supported links in their Web API, both for users and bots. It just happens the Slack client doesn't use that feature.
Hey this is neat! Re: injecting into Slack.app, you're right, it's a pain. I had a simple approach here: https://zachsnow.github.io/slinger/ but it needs to be updated for every version (which of course I didn't do).
It would be cool if you made it so that users could inject it manually (via enabling --dev and $.getScript() or so) into the app; I for one don't restart Slack very often, so it wouldn't be too much of a pain.
One of the problem I always have on Slack or other chats is the 300+ unread messages after being offline for a day or two. I tend to skip everything but sometimes I miss things I should read...
I think it's a common misunderstanding that we must read everything in Slack. You don't have to. If something's important it will come up again, or if it's directly relevant to you then someone will tag you. When someone asks about a Slack conversation you didn't see, just say you missed it. It's a better norm than being expected to stay up to the minute on every word uttered by every employee.
Anything important enough that should not be missed should be sent in an email. Slack, IRC, and other chat-likes are additional communication channels—they shouldn’t be a primary mission-critical delivery system.
what would you like it to happen? the extension may be able to filter the ones sent in the last N hours and adjust the number of unread... but that wouldn't solve the problem of missing things you should read.
[+] [-] fb03|7 years ago|reply
Then someone invited me to try Discord for company comms and I said "that's a gaming-oriented app, cmon it won't work well".... my mind was blown by how smooth Discord is.
We are a small shop but since we migrated from Slack to Discord we haven't been focusing much on 'how to communicate' but more on actually just chatting.
I advise everyone that talks about Slack to try Discord as a good alternative, even if your use case is synchronizing a loosely-knit team over the internet.
[+] [-] brobdingnagians|7 years ago|reply
[1] https://www.reddit.com/r/discordapp/comments/3q62hw/on_what_...
[+] [-] kmf|7 years ago|reply
I strongly recommend Discord over Slack for public chat groups; I'd happily use it over Slack for company chat as well, with the caveat that the integration/app story isn't quite as far along as Slack is.
[1]: https://byteconf.com/discord
[+] [-] buf|7 years ago|reply
Plus I pay nothing.
[+] [-] LinuxBender|7 years ago|reply
[+] [-] g3rv4|7 years ago|reply
[+] [-] leppr|7 years ago|reply
[+] [-] graeme|7 years ago|reply
[+] [-] tmoravec|7 years ago|reply
[+] [-] oweiler|7 years ago|reply
TL;DR
Discord explicitly confirms in its privacy policy[1] that it collects the following information:
IP AddressDevice UUIDUser's e-mail addressAll text messagesAll imagesAll VOIP data (voice chat)Open rates for e-mail sent by Discord
[+] [-] danShumway|7 years ago|reply
> The nice part? it shows it as a link for everybody, not only those who have the extension installed.
Wait, wat? I'm looking at the code[0], and this is the most surprising part of this entire project to me. Slack goes out of its way to say "we don't support Markdown because we think the link support is an exploit." But they just have an alternate, undocumented way to send links anyway?
Is that a bug on Slack's side? I'm trying the syntax format that you're casting to in DMs to myself, and it doesn't seem to work? Are they doing clientside escaping or something?
Don't get me wrong, I think the "people might phish links" excuse is kind of lame when there are multiple ways for them to mitigate that problem, I'm just very curious about how and why this works.
[0]: https://github.com/g3rv4/BetterSlack/commit/24ad3b57da7a9c9c...
[+] [-] g3rv4|7 years ago|reply
If they do, I'll fix it on the extension (so only people with the extension would see the markdown links as real links).
Also: to answer your question... yes, there's an undocumented way of sending them. And yes, the client escapes `<https://url.com|the title>` to `<https://url.com|the title>`.
The format is the same format used by bots to generate links.
[+] [-] Savageman|7 years ago|reply
[+] [-] zachsnow|7 years ago|reply
It would be cool if you made it so that users could inject it manually (via enabling --dev and $.getScript() or so) into the app; I for one don't restart Slack very often, so it wouldn't be too much of a pain.
[+] [-] g3rv4|7 years ago|reply
But that sounds like an amazing thing for me to use locally :)
[+] [-] geekuillaume|7 years ago|reply
A solution?
[+] [-] emddudley|7 years ago|reply
[+] [-] weego|7 years ago|reply
[+] [-] bproven|7 years ago|reply
[+] [-] dorfsmay|7 years ago|reply
Just an FYI that everybody needs to know or needs an answer regardless of when you can answer: use email
Information that is valid until a major change (or forever if that exists): document in your wiki or whatever documentation system you use.
When I'm back from time off, I mark all slack channels as read.
[+] [-] vishnu_ks|7 years ago|reply
Disclaimer: I am a full time contributor at Zulip.
[+] [-] bobwaycott|7 years ago|reply
[+] [-] andrewkfiedler|7 years ago|reply
[+] [-] g3rv4|7 years ago|reply
[+] [-] prolikewh0a|7 years ago|reply
[+] [-] targafarian|7 years ago|reply
[+] [-] g3rv4|7 years ago|reply
PRs are welcome :)
[+] [-] NelsonMinar|7 years ago|reply
[+] [-] g3rv4|7 years ago|reply
[+] [-] robmccoll|7 years ago|reply
Slack always seems like a step backwards in chat to me.
[+] [-] g3rv4|7 years ago|reply
[+] [-] stunt|7 years ago|reply
[+] [-] g3rv4|7 years ago|reply
however, anybody with a bit of javascript knowledge can do it. I guess we need to keep educating people about the importance of checking urls?
[+] [-] gcb0|7 years ago|reply
[+] [-] pingec|7 years ago|reply
[+] [-] brootstrap|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]