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
freeatnet 🗿🎩
@freeatnet.eth
We added a tutorial on tuning Discord notifications to our onboarding 6 months in 😅 Too many people just go "well having 600 notifications per hour is just my life now"
1 reply
0 recast
1 reaction
Boiler(Chris)
@boiler
This is probably the first algorithm I set up on a server.
3 replies
0 recast
1 reaction
freeatnet 🗿🎩
@freeatnet.eth
I know what you mean, but I still want the team to have access to @everyone, I just want the service to handle it more intelligently. We all made fun of Slack's super complex notification flowchart a few years back, but I see why it exists now.
2 replies
0 recast
0 reaction
freeatnet 🗿🎩
@freeatnet.eth
More specifically, scheduled DnD times + ability for the sender to override the DnD make a huge difference (between "@everyone don't forget to send in your secret santa details this week" and "@everyone production is down, all hands on deck")
1 reply
0 recast
0 reaction
justin.framedl.eth
@ahn.eth
It's always overkill until it isn't 😂
0 reply
0 recast
1 reaction
