Firefox doesn’t implement the AudioData API, which is probably necessary for the waveform viewer and cropping tool Discord presents in the soundboard management UI.
Not everything is about Chrome DRM yall.
Edited to add screenshot of spoofing user-agent on Firefox and getting an error:
Yet another experimental API only supported by Chrome. Chrome has always been like this, implementing experimental API that hasn’t been finalized yet. You might say they’re innovating to support new technologies, but actually it’s more like they’re doing whatever they pleased, as demonstrated by their removal of jpeg xl support despite web communities plea not to do so (a new more efficient image compression, but not made by Google so screw it), pushing manifest V3 and ad topics, and recent push for web environment integrity API.
How can they not support jpg xl? It’s such a huge thing
Discord is such an obvious “stay the fuck away from” product.
With the same critical mass of users that most proprietary social media have, unfortunately. You’ll be lucky to find certain communities on Matrix at all.
I’m a little baffled by this one. File upload isn’t exactly some new HTML5.1 feature or anything. There’s no good reason they can’t have this handled properly.
EDIT - just for some additional context, I’ve never used this feature so I had no idea it was more than a mere file upload. Looks like Discord has chosen a non-standardized API that’s currently only in Chromium, but if it were up to me I’d try to budget some time for a simple fallback in case someone’s using Discord in Safari or FF.
I bet if you switch user agents it works just fine.
Here’s what happens when you spoof a Chrome user-agent.
deleted by creator
