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.
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.
EEE yall
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.
If you clicked the link. It says experimental technology. It's not mozilla's fault Chrome is adding features that are not standard. Sites like Discord for utilizing non standard API's.
It appears the Reddit users that don't read further than the title have arrived on Lemmy.
Shocking news: people are people everywhere, not just on 'rival' platforms.
And their desktop client technically is a browser without omnibar.
Electron is not just a browser. It's more like a native app framework that just happens to use HTML and CSS to render UIs. You can do anything the OS lets you do, not just what a browser environment would let you do.
Electron is an unholy fusion of Chromium and Node.JS. Nothing more, nothing less. It doesn't 'just happen' to use HTML and CSS. It's literally just a browser with most of the default browser UI being hidden. Something like React Native would better fit your definition.
It's not literally just a browser. It's literally just a web engine with a full set of OS calls hooked in. It is not a browser in the same way GNOME is not an OS. A browser comes with a whole lot more than a web engine, so calling it "a browser" is wrong both technically and colloquially.
I'm on my lunch break from working on a React Native codebase, and I wouldn't say RN fits that definition at all... but I think we're just getting lost in semantics.
My point was just that a web app running inside a browser has to abide by the rules and limitations set by the browser, whereas Electron flips that relationship -- your app sets the rules and limitations of what can be done, and the web rendering process abides by whatever environment you create. You can do anything the OS permits. Even from inside a web context, if you want. You don't need a browser-managed sandbox to mediate your interactions with the OS.
But probably Chromium right? They probably didn't make all Discord functions work for Firefox as that would require some extra work probably.
Yes, electron.
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.
It’s probably the AudioData API.
There's really no reason to be mad at them in this particular instance. Their client is Chromium-based (Electron) so they will optimize their new features for that engine first. There's probably less than 5% users who Discord from browser, let alone Firefox, and I think I'm being generous with that number. Additionally, some things are harder to implement (or even impossible) in native web rather than Electron, that has all the NodeJS integrations.
File upload is not a chromium feature, it's a super old basic feature. It's just their pittiness and upcoming drm implications. I bet if you set your user-agent to chrome it woould work just fine.
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:
https://midwest.social/pictrs/image/4edb0d24-0c2a-4610-b7b2-eed07a3c7d24.png
Here’s what happens when you spoof a Chrome user-agent.
https://midwest.social/pictrs/image/d3b96401-956b-4eab-bc5c-64b0743feae4.png
-kibiz0r@midwest.social
This dialog doesn't do just file upload, after you upload you can cut the sound file into a 4-second clip, inside the client. My bet is that it might technically be possible to do it in Firefox, but not with the same exact code as with chromium, and thus they decided they don't care.
I ditched Discord a few weeks ago. I moved to Matrix!
Not to be discouraging, but i managed to quit discord for a few months, but i returned again, turns out many projects, even open source, use discord for discussion only
codes a desktop OS specific program coded in C just to spite you
To be honest I absolutely hate everything being a browser app.
element / matrix instead
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 said 'fuck you" to Slack for similar reasons. Going to same the same to Discord now.
Eventually I can see discord discontinuing their web client to push you users into installing their spyware.
There is FOSS wrapper for discord called webcord, if you have to use discord but want a bit more privacy.
People use discord in the browser? Damn boi
Never use an app for what should be a web site.
It works better for me as an app. I don't like my browsers to be cluttered like that. But if it fits your usecase
This is a most excellent place for technology news and articles.
