Invasive Species
Invasive Species
Yes, but only begrudgingly.
(edit) oh no, Iāve said something bad about the lesser evil, and the people who have made it their identity to violently cum all over the first thing that isnāt owned by Google are after me. I hope the pipe bomb hitman is at least polite.
I wish this blanket statement were true. Firefox is better in some respects, but surely not all. Tab and session management - just to name two examples - are just handled better by the Chromium crowd, as much as it pains me to say that.
That said, I still use Firefox in most cases.
Looks like it didnāt work unfortunately š Thank you for the suggestion though!
Ah. I guess I donāt notice that since Iām on Linux and just update Firefox whenever I want.
If you go to Hamburger menu > Settings > General > Check for updates but let you choose to install them, you wonāt auto update anymore. I agree that would be annoying.
From what I understand, Chrome doesnāt need to do this, because when you close it, it keeps running in the background and does its upgrades then, which is also pretty intrusive.
If youāre updating Firefox via the built-in auto-updater, you can tell it in the settings that it should only install updates when you tell it to do so.
When it happens, it doesnāt let me do anything other than stay on the already loaded webpage without restarting.
Open a new tab > āRestart to continueā¦ā
Click a link > āRestart to continueā¦ā
Type a URL > āRestart to continueā¦ā
and etc
Iāve had this same experience on Linux Mint. Iāll run apt update & apt upgrade and, occasionally, if Firefox is one of the things being updated, new tabs and new pages wonāt load and will tell me I need to do a system restart to continue browsing.
I always update manually, so it never happens without me initiating the update first. But sometimes Iām like, āDangit, didnāt realize this update would require a restart to keep using Firefox.ā
I found this. superuser.com/ā¦/how-can-i-make-firefox-stop-forciā¦
On Linux, disabling Firefox updates in Firefox itself will not fix this issue, because Firefoxās own updater doesnāt actually have this bug! You get this warning when the Linux package manager has already replaced the files underneath the running program.
You say itās windows, but I think you said itās a work machine so maybe theyāre updating firefox from under you?
Different profiles on Firefox are nowhere near Chrome.
Iām still going to use FF, but there are areas it lags behind Chrome. Thatās the only big one for me.
And to make things even more difficult,
I really want there to be more options in the browser market that arenāt Blink based (or WebKit, sorry Apple), but the situationās tough.
Iām an advocate for Firefox, but it is slowly, slowly entering enshittification.
The addition of AI, dark patterns to enable āsponsored bookmarksā upon reinstall, ads (albeit subtle) when using the address bar for searchā¦
All of these can be disabled, some easily, some with feature flags.
Sure the enshittification isnāt anywhere near the pace as Chrome but itās happening. And again, this is coming from a maybe 10 year financial donor to Mozilla.
Firefox is better than Chrome, no question but there is an opportunity for a new browser to challenge the field.
You make good points but some people are knew jerking on Firefoxās AI. One of them is client side translation which is really neat as I donāt need to send the content to some Google ad data vacuum.
Another AI model helps differently abled people to have websites described to them using, again, a local model.
There is also Libtefox which uses the same rendering engine without the other stuff if you donāt want it.
I consider it an important act to use non Chromium browsers as not to completely hand over the power of rendering web content to Google.
Chromium is deprecating manifest v2 and the newer v3 has neutered ad blocking capabilities. In Alphabetās SEC fillings they list ad blocking as a challenge to their revenue. End users canāt just flip v2 back on (unless the devs of their browser put work to let them). End users can change their default search engine though. Very easily. Trivially so. Who knows, maybe as a result of that court ruling weāll see browsers forced to have no default search engine in the future. I think thatās better, yes, but I really donāt think having Google Search as the default is that massive of a concern compared to much of the other shit theyāre doing.
There is nothing personally-identifiable in the data Mozilla collects in Firefox: support.mozilla.org/en-US/kb/telemetry-clientid
Technical data includes information about your Firefox version and language, device operating system and hardware configuration, memory, basic information about crashes and errors, outcome of automated processes like updates and safebrowsing. When Firefox sends data to us, your IP address is temporarily collected as part of our server logs. IP addresses are deleted every 14 days.
I guess, this is most of the changes they do: librewolf.net/docs/features/
Thereās maybe a handful where Iām not sure, if you can do them via settings.
One where itās technically the case, is that they remove Pocket at compile time. But to my knowledge, Pocket integration is pretty much a glorified bookmark. Thereās not much code to remove. And it can be disabled via about:config by setting extensions.pocket.enabled to false.
I guess, to be fair to LibreWolf, Mozilla has been helping out the Tor Browser devs since forever, so most things needed for Tor Browser are just a toggle in the Firefox settings.
As a result, though, thereās also lots of settings, which partially need expert knowledge. So, there is definitely room for different presets. But yeah, still leaves the question, whether one really needs a different executable to adjust these settings.
Itās unfortunately a relatively complex thing to answer.
First off, thereās the license. The source code is published under a BSD-3 license, which is very permissive, meaning in theory, anyone could fork the repository and be completely free from any control of Google.
However, this is not really a thing in reality.
First of all, for your fork to have any meaning at all, you need people to use it. Theyāre not going to use your fork, if itās unclear whether youāre trustworthy and in particular, you need to offer something better than Google and do so for a while, so that people feel like they can rely on you.
In particular, Google is not bound by its license to make future updates available under the same license. If your fork would become too successful, they could re-license and then it would genuinely just become a competition for who has more dev power.
But with the caveat that if you donāt also re-license, then Google can continue taking your work and provide theirs on top.
In particular, Google also has a load of tracking infrastructure and an ad business, which makes Chrome a valuable investment for them.
Thereās very few other organizations for which it would make sense to invest similarly much into Chromium development (and those organizations will then have similarly awful motivations).
Which means a hard fork, i.e. without dependence on future updates from Google, is pretty much not going to happen.
You also need a solid number of users in your fork, if you want to have any say in terms of web standards. So long as Google Chrome has a majority of users, Google can easily introduce proprietary standards, which webdevs will gladly lap up.
So, all in all, Google does have a pretty tight grip. Presumably, they donāt put any incriminating stuff into Chromium, so that they steer clear of even faint attempts to fork (and because they can just put those into Google Chrome instead). But thereās plenty room for interpretation in most web standards, so they can implement them in their interest, and then the forks have to stick to that implement, if they want to remain compatible with the web.
Download Firefox/ Look inside/ Still Firefox.
Download thunderbird/ Look inside/ Older Firefox.