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.
Sounds… disappointing, really. While the feature of track blocking sounds appealing at first, that feature is the main reason I abandoned Firefox (after 15 years of using it) and all FF-like browsers that have it. More and more websites stop functioning properly with tracking blocked and I can’t login to my profile. With these particular sites I have nothing to worry about tracking but unfortunately even with disabled tracking protection, they still refuse to let me log in. It’s unlikely that the websites would remove the tracking functions, so until the developers of FF and FF-like browsers find a way to circumvent this problem with logging in, I don’t see a reason for me or anyone else to use such a browser.
deleted by creator
I was just installing the dot-bin package but ran into a conflict with graphviz. Looks like someone already brought it up: https://aur.archlinux.org/packages/dot-bin/#comment-810274
The pre-built release worked for me though. I poked around a bit and I kind of like it so far! I’ll have to play around a bit more, but it’s nice to see gecko getting some love.
I’ve never had that kind of problem, where do you usually run into them?
idem, i have tracking protections enabled on strict, ub o blocking all third party stuff, first party isolation enabled, fission enabled and i have no issues
Hi, I’ve been reading about Fission. I didn’t see this option on privacytools.io, still would you recommend it? Thanks
It is still only available in Nightly, for basically it isolates every website from each other, it consumes a lot of ram tho so I wouldn’t recommend it if your are in an older system, otherwise is awesome for privacy.
I have the option in about:config for updated Firefox. Thank you for the advice, I think I’ll keep it on
Gamivo and Kinguin, mostly. Also mediafire. Mediafire keeps saying “this form has been idle for too long”. All the browsers that have some kind of track blocking have this problem with these sites, regardless of the engine. Only Chrome and Chromium don’t have that feature and I have absolutely no problems to login to my profile.
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.
you can submit a report to webcompat.com and hopefully the Mozilla team will fix it
Thanks! Will do.