justin.framedl.eth
@ahn.eth
Our company, 100% remote, decided to shift from Slack to Discord for communication/collaboration Good decision, bad decision, no difference?
20 replies
1 recast
21 reactions
Manuel
@manuelmaccou.eth
It depends on what your employees are used to, what they’ll do there. I love Discord and I haven’t seen 1 argument that holds up. There’s only a lot of notifications if you turn them all on. It’s very easy to granularly change them. Communication organization is great between all the different channel types.
2 replies
0 recast
2 reactions
justin.framedl.eth
@ahn.eth
Yea, I think we're mostly Slack first people. But since our Discord product is by far more used than our Slack one, this decision was made so we can prioritize and better understand the Discord side of things. Any other best practices (settings, apps, etc.) you can share off the top of your head?
4 replies
0 recast
1 reaction
humpty
@humpty
I’d recommend not using Discord for business comms. Slack is a superior product. And more secure. But since you build for Discord, it makes sense to dogfood the platform.
1 reply
0 recast
0 reaction
Mark Fishman
@markfishman
Mad respect for this decision 🫡
1 reply
0 recast
0 reaction
Boiler(Chris)
@boiler
Not sure where you are at in your journey with discord settings or not. There are tons of tricks. Getting used to how roles work and what you can do with them is important. For example you can organize the roles in the right menu, in the settings.
1 reply
0 recast
0 reaction
Manuel
@manuelmaccou.eth
Yea I think the decision makes sense then. I’d recommend getting very familiar with permissions for the server and individual channels. If you need help, hit me up any time. Also find a simple “proof of human” bot. Unfortunately a lot of them are overly complicated. Captcha may be a good option
0 reply
0 recast
0 reaction