It appears the Reddit users that don’t read further than the title have arrived on Lemmy.
Comment on "...is not supported in this browser", fuck you Discord
kibiz0r@midwest.social 1 year ago
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.
HKayn@dormi.zone 1 year ago
Pfnic@feddit.ch 1 year ago
Care to elaborate? I can’t make sense of your response
EdibleFriend@lemmy.world 1 year ago
For some god damn reason he’s trying to turn this into a ‘reddit bad’ discussion.
franklin@lemmy.world 1 year ago
Yeah unfortunately it looks like they are here too, oh well at least it’s money out of spez’s hands
Prethoryn@lemmy.world 1 year ago
Thank fucking people like you. The average Lemmy user just knows everything.
I have seen so many Lemmy users think they are better than Reddit users. Truth is, you are all fucking ass holes you are just different kinds of ass holes.
None of us agree with Google’s choices but for fucks sake not everything is because Google chose it.
Sometimes it’s just in the damn browser. Like fuck off.
I use Chrome and Firefox and have two different online personas with both.
redcalcium@lemmy.institute 1 year ago
Yet another experimental API only Chrome supports. 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.
warmaster@lemmy.world 1 year ago
EEE y’all
ILikeBoobies@lemmy.ca 1 year ago
How can they not support jpg xl? It’s such a huge thing
lud@lemm.ee 1 year ago
Firefox and Safari is also implementing experimental features often.
ferralcat@monyet.cc 1 year ago
I think Moz helped write and supports this. I even think it’s (partially enabled in nightly?)
Not sure if these built in decoders are supported though. Seems a bit dangerous to expose native codecs directly from the web to be honest, since you’ll end up with wildly varying support across browsers.
Anonymousllama@lemmy.world 1 year ago
I remember ages ago websites were all focused on “works best on Internet Explorer” or “please use Netscape for the best experience”
We managed a good solid decade after that where browsers all somewhat caught up to each other and now we’re going back that way again, with each website just YOLO implementing APIs that aren’t fully supported.
When you did that back in IE7/8/9, you missed out on rounded corners or drop shadows, now whole parts of apps won’t work unless you’re on chrome 🤯