cross-posted from: https://lemmy.ml/post/67935
New gecko based browsers are rare nowadays but this one is especially unique to me because it is more than just “firefox with tweaks” like a lot of the ones I’ve come across. The UI is different, it’s working on custom settings, a new more powerful sidebar, a new theming system, and potentially IPFS/Dat support further down the line. It’s very early in development but it’s still impressive as it is.
FF recently enabled a feature to make some websites run smoothly when they would typically get broken by the tracking protection.
Sounds good. Gamivo and kinguin did let me in but mediafire still doesn’t. Unfortunately ever since they disabled the feedback feature, I have no way to report this problem to them and my only hope is that employees of Mozila might be reading this community here.
Firefox mediafire: https://i.imgur.com/kJUBHiH.png
Google Chrome mediafire: https://i.imgur.com/QVyjZmZ.png
Mediafire is my secondary online backup for stuff and until Mozilla fix that problem with mediafire, for me there’s no reason to use Firefox. Don’t think I enjoy using Chrome (or Chromium), though, or that I’m hating and trolling Firefox. I’m not. But for the moment only Chrome works the way I need + it has extensions Firefox doesn’t have yet. Secondly: Firefox doesn’t recognize the instagram images as images whereas a Chrome extension does and I download and/or search them on TinEye a lot. But the moment these issues are fixed in Firefox, I will return to that browser. The reason I have subscribed for the Firefox community here is that I’m waiting for the version that will have these issues fixed. Hopefully until then someone would have written an extension to replace the removed function from the context menu - “view image details”.
Why don’t you try creating a new profile, enabling tracking protections on strict and trying to log in? Maybe some of your extensions are what causing the issue.
I’ve tried that (clean profile) when FF was v86. Mediafire still wouldn’t let me in, that’s how I discovered it was a browser problem and not an extension problem.