I'm really impressed. I was using Discord for most of this weekend, specifically Friday and Saturday. Never noticed any issues.
They don't have a posted outage for Saturday, but I noticed issues with it on Saturday evening/night I believe. I'm wondering if it was related to the issues that they included in the post-mortem.
Discord Postmortem from Friday
11–20 of 45 posts
Re: Discord Postmortem from Friday
#12Earlier quoted context omitted.
Weird, I find Discord's audio quality especially to be terrible. And their lack of scalable monetization leads me worried about its longterm success as a platform - they are adding more cost-intensive features and continuing to try to support it with what is essentially a $5 monthly donation model.
Can you give more explicit examples of the bad audio quality you experience? I'd be happy to forward this onto our native team to look into if there are some concrete things they can look at. Generally 99% of the audio issues we see people experience are due to ISP/peering/DDoS/etc issues, most of which are handled automatically by our servers within a few minutes.
Complaints aside, I love the service. Echoing what avree said, long term monetization worries me. I would like to see discord survive, but its story looks similar to Trello right now in terms of monetization.
Re: Discord Postmortem from Friday
#13Earlier quoted context omitted.
Can you give more explicit examples of the bad audio quality you experience? I'd be happy to forward this onto our native team to look into if there are some concrete things they can look at. Generally 99% of the audio issues we see people experience are due to ISP/peering/DDoS/etc issues, most of which are handled automatically by our servers within a few minutes.
Anecdotal, but direct calls are pretty unusable for me. I'm on the west coast, and when I attempt calls to the east cost, it frequently cuts out. The workaround was just creating a server and using a voice room in it. This had drastically higher call quality. I assume this is ISP/Peering related, but to see such a night and day difference between voice channels and direct calls leads me to believe that there's someth…
Re: Discord Postmortem from Friday
#14I'm really impressed. I was using Discord for most of this weekend, specifically Friday and Saturday. Never noticed any issues.
Re: Discord Postmortem from Friday
#15Does anyone use discord for work?
I have used Discord quite a bit for gaming, but it hasn't proved a better option than Slack to me (at least in a work context).
Re: Discord Postmortem from Friday
#16Re: Discord Postmortem from Friday
#17Does anyone use discord for work?
We're stuck with Skype for official stuff and telephony though.
Re: Discord Postmortem from Friday
#18Earlier quoted context omitted.
Weird, I find Discord's audio quality especially to be terrible. And their lack of scalable monetization leads me worried about its longterm success as a platform - they are adding more cost-intensive features and continuing to try to support it with what is essentially a $5 monthly donation model.
Can you give more explicit examples of the bad audio quality you experience? I'd be happy to forward this onto our native team to look into if there are some concrete things they can look at. Generally 99% of the audio issues we see people experience are due to ISP/peering/DDoS/etc issues, most of which are handled automatically by our servers within a few minutes.
FWIW, it generally works pretty well, and overall, Discord is a fantastic product that I'm happy to be using.
Re: Discord Postmortem from Friday
#19Re: Discord Postmortem from Friday
#20At this scale, it seems like it may be warranted to start using reliability testing in production in like with Netflix.
At the end I see mention of a library with flaws. I am curious as to which library that is, given I develop some projects in Elixir.