Pet peeve of mine: as I understand it Discord labels each of its communities as "servers". That's why you've probably encountered youngins calling subreddits or group chats "servers" lately. That's obviously a misnomer since it's not like they're technically independent servers (as showcased by this crash).<p>It's just vocabulary but for somebody like me who still hangs onto IRC even though it's been almost entirely displaced by proprietary and centralized solutions like Discord it really feels like they're rubbing it in. Just co-opting decentralized lingo with none of the actual features.
Is anyone else pretty bothered that popular services like Discord can and do read all of your 'private' messages in plaintext, and when/if they are bought out, all of your chat and usage history will be sold to an unknown third party along with the company?<p>I wish at some point we'd see <i>mainstream</i> messengers that put actual effort into respecting the user, along with their autonomy and privacy. It'd be amazing if we could actually <i>directly</i> (from a technical perspective) message other people, without needing central servers between us.
microsoft teams failed too today so I reverted back to email.
slack had downtime aswell.<p>None of these were prepared for the massive surge of users working from home.
My work set up Discord for voice chat during WFH despite mine and my colleague's efforts to promote setting up a Matrix server with federation disabled.<p>We self-host just about everything else ourselves, but for some reason everyone flocked to Discord.
I also got problems with Safari Books Online around lunch time.<p>But our Microsoft Teams meeting in the morning worked pretty well. Even that everyone was calling from home. (That is 10 connections while usually is just one meeting room and a couple of people from home or another location).<p>Google Photos search was also stuck for several seconds before getting results.<p>In general the web felt slow most of the day. I am not surprised that Discord service is suffering.
<p><pre><code> A series of fatal errors caused the majority of servers to become unavailable. We are working to revive all of these resources. Most users will be unable to connect while this work is ongoing.
</code></pre>
That's microservices for you. Instead of one fatal error you have to fix there's multiple in different codebases at the same time