Discord already uses Cloudflare, I'm curious what they think of Workers.
edit: I'm on macOS, not an heavy user, I used Slack / Skype / Hangouts / WhatsApp / Messenger / etc. before
Discord already uses Cloudflare, I'm curious what they think of Workers.
edit: I'm on macOS, not an heavy user, I used Slack / Skype / Hangouts / WhatsApp / Messenger / etc. before
- Abusive trust and safety team - Constant outages for both users and bots - Frontend is heavily bloated - UI designed for money grab instead for the users
While I appreciate their technical accomplishments, this is one of those things that gives me chills about the company.
Don't fall in love with services. (Or with people ;P)
Not to mention where an update randomly the noise suppression would completely mute your mic.
We are a very heavy user of cloudflare workers. Our marketing/developer/web app are entirely served from the edge using workers - and we use workers for request authentication for downloading game chunks on our store.
Discord has actually been using workers since before they were available to the general public. They've been using them mainly for edge caching games for the store, A/B, and promotion of clients to different testing environments.
Never in the world would I have thought a gaming chat client had more robust features than the pricey enterprise chat client
It's the replacement for the vintage volume control, while a little sub-par by any modern standard, you can pick the input/output device per application
No offence but that's like your opinion.
Coming from IRC and TeamSpeak, to me Discord is unnecessarily bloated and full of analytics.
>I used Slack / Skype / Hangouts / WhatsApp / Messenger / etc. before
Yeah, explains it. :P
The voice service isn't very high quality and there are frequent server outages.
I use Telegram, Facebook, whatever except Discord for instant messaging, and wish Discord wasn't the default for non-professional groups.
People my age (upper 20s) praising it are always those who used Skype for gaming and never touched Teamspeak/Ventrilo/Mumble.
As gaming itself got broader reach a lot of casual folks were left to their own devices and underserved, so that’s the big gap being seen. I know plenty of 20-somethings that know about and used the predecessors to Discord but they’re all hardcore gamers compared to even the folks closer to mid/late 30s that may have been hardcore before but don’t have the time to fiddle with these systems anymore.
It seems with Discord quality was tough to maintain at scale and we’ve got the inverse problem set.
And it is, of course, closed source, so no way to use an alternative client. I wish I could use an IRC gateway for it, that would be cool (I very, very rarely use the voice chat)
Just because something is closed source, doesn't mean it's impossible to reverse engineer. The entire system is compiled into a javascript webpack, alongside just reading web requests/their documentation, doing some basic functionality in an alternative implementation is really easy.
This apparently breaks the terms of service, but they are only enforce this if you're an outlier for the number of API requests you send.
The most well known 3rd party client would be Ripcord, which I use for it's Slack features
This thing usually goes: Until the better client threatens the proprietary one with is better monetized.
Now, you might want a bouncer to store messaged and logs when offline, but not to be able to connect to multiple servers. Logging is a basic feature in IRC.
Then I know they're reading.
>and you have no idea who might be saving logs or where they might be publishing them
If I'm in a room with you nothing stops you from telling others what I've told you.
Sure, but I won't have a complete written record like an IRC log, and won't be able to credibly quote.