The issue I have with the TOR browser (as an example of an actual real fork) is that they only stub away the APIs they know of, they don't really remove them and from time to time other methods of tracking glitch through; including all the fingerprinting requests when opening a fresh browser session.
I guess with a hard fork they couldn't keep up with upstream.
But honestly, I would totally be okay with a browser that doesn't have modern Web APIs because literally all of them from the last 10 years were just integrated to allow "appifying websites".
If I wanna see a fancy WebGL demo I can also use a temporary chrome, but my main browser should not have that amount of (unmaintained) attack surfaces.
All "forks" of Firefox usually aren't forks but just profiles with user.js configs. The only real fork of the engine itself is Pale Moon, and that project is a political shitshow and super outdated (which would be okay if it focussed on stability instead).
I guess with a hard fork they couldn't keep up with upstream.
But honestly, I would totally be okay with a browser that doesn't have modern Web APIs because literally all of them from the last 10 years were just integrated to allow "appifying websites".
If I wanna see a fancy WebGL demo I can also use a temporary chrome, but my main browser should not have that amount of (unmaintained) attack surfaces.
All "forks" of Firefox usually aren't forks but just profiles with user.js configs. The only real fork of the engine itself is Pale Moon, and that project is a political shitshow and super outdated (which would be okay if it focussed on stability instead).