lol
Hug Firefox close, it's an awful world out there, especially with Google being given the greelight to continue their monopolising with Chrome.
I remember being tempted by this thing when it first came out - their asinine sign up waiting list kept me from pursuing it further and then I forgot about it until they eventually fully dumped it and moved into full AI-enshittification territory. There are really 30 years of reasons why most people will never trust a new entrant to the browser market - this is just the latest and probably greatest.
What a shitshow.
> their asinine sign up waiting list kept me from pursuing it further
Yeah, this -- combined with the fact that their website told you nearly nothing about why their browser was worth signing up to something just to try it out someday -- is why I never used it. I don't personally know anyone who did.
It seemed dumb at the time -- I was actively looking for a better browser and certainly would have considered Arc, but they were determined to keep me from learning anything about it (let alone try it), so that never happened.
You mean the browser primarily funded by Google giving Mozilla a giant bucket of cash every year to be the default search engine for?
Am I the only one having isses with Firefox on Linux? While playing videos the image sometimes freeze and the audio keeps playing. Ironically the best media-player so far has been Edge, even chrome have some issues. All installed from Fedora discovery store, so prob related to Flatpak packaging.
I'm on Gentoo using the firefox-bin package - things work great. Spotify all day, YouTubes, Vimeo, Zoom - even Teams works.
Yeah, same on Debian.
Even Teams video calls work fine. A lot of times it works better than the Windows client I use at work.
No issues browsing or playing media on Mint XFCE, but I'm not using Flatpak.
On old hardware (~10 year old laptop with a Core i5-5200u and integrated graphics), I do have trouble with Google Video calls lagging. This seems to be caused by a combination of old hardware and certain Google products being overly optimized for Chrome.
My guess is that you don't have hardware acceleration enabled. That could be due to Flatpak packaging, or it could be due to running a less-than-optimal graphics driver. Granted it's been awhile since I've tried the open source graphics drivers and I hear they have improved, but I've had better success with closed source graphics drivers.
flatpaks are sometimes funky with highly optimized software - they tend to need lower level access to hardware, which flatpakking sometimes gets in the way of.
check if you have hardware acceleration, maybe other stuff? `about:support` has lots of info, I've had to tweak a few things routinely to get browsers working like their native counterpart.
I personally don't have that issue with Netflix and Youtube on Firefox in kde-neon.
I have no such issues (Debian), but I also don't use the flatpak.