Starting with the next major release, Chromium will stop supporting Manifest V2 extensions. The change will affect users who have clung to uBlock Origin in Chrome, Edge,...
Totally agree with your comment, I’d just make an observation to this specific part:
but a new rendering engine is necessary
The problem with a new rendering engine is who have influence over the specs/standards, as well as who holds the necessary keys to be granted access to its features. We humans have been tying ourselves to centralized entities who pinky-swear they can guarantee “Safety/Security”: SSL/TLS, HDCP and any other technologies gate-kept by “Divine Beholders” of the only keys able to “bless mere mortals” with the temporary grant required to develop using a technology. I mean, this is exactly what’s happening to mobile apps, with “sideloading” having been a boogieman word for installing apps without having to rely on a centralized app store, a manufactured consent that worked so well that people and governments have been accepting, even relying on, Google’s “Integrity Check” shenanigans (and the Apple’s whatever analogue i-thing for iOS). The supply chain attacks that have been happening (from PyPi to AUR) feels like something that’s further pushing us to more centralized “authorities” who’ll then have absolute power over who can and who can’t pass.
Even if a truly independent entity were to come up with a full-fledged browser engine, as compatible as possible with current specs, Google still seems to possess lots of influence on the official Web standards and they can simply commit changes to the specs that would uncirvumventably require Google’s “blessing” to function (for your security, of course /s); so anything “not blessed” would simply fail to function because it isn’t signed by the “blessing”, “divine” keys.
And Mozilla doesn’t feel trustworthy as well, especially because they’re overly reliant on Google’s money to exist, and also because they’ve been pivoting to opt-out (so one must explicitly disable it and confirm their will to disable it, otherwise it will be on by default, which turns to be a shady lack of consenting, much like Google’s behavior) “features” much despite of their own userbase’s demands.
This said, I used to believe in third-way projects such as Servo and Ladybird… except the latter went down a very unacceptable road (founder turned out to be a transphobe who dismisses using neuter pronouns and assumes the user’s gender to be always a “he/him” because “we don’t do politics here”), and the former… it belongs to Linux Foundation, where big corps such as Microsoft, Google and Oracle have their horses (after all, “Microsoft loves Linux”; sure, Nadella, we know how Microsoft “loves” Linux /s).
I’m afraid there’s no light at the end of the fiber optics (pun intended) when it comes to alternative engines: either we try to actively boycott the “modern Web technologies” altogether (ditching HTTP(S) and pivoting to entire alternative protocols such as Geminiprotocol and Gopher whose standards/specs are slightly more distant from the dirty hands of “Google et al”; worth mentioning how Fediverse has Geminiprotocol-capable platforms such as tootik, it’s more doable than reinventing the cursed wheel of the Web which turns to be the infamous Chromium wheel) or we try to stick with the “lesser evil” (forks of Mozilla Firefox, until Firefox becomes totally enshittifiedly indistinguishable from Chromium) until a solution happens (or likely not, then we’re left with just the other path, which is pivoting to alternative standards altogether).
Totally agree with your comment, I’d just make an observation to this specific part:
The problem with a new rendering engine is who have influence over the specs/standards, as well as who holds the necessary keys to be granted access to its features. We humans have been tying ourselves to centralized entities who pinky-swear they can guarantee “Safety/Security”: SSL/TLS, HDCP and any other technologies gate-kept by “Divine Beholders” of the only keys able to “bless mere mortals” with the temporary grant required to develop using a technology. I mean, this is exactly what’s happening to mobile apps, with “sideloading” having been a boogieman word for installing apps without having to rely on a centralized app store, a manufactured consent that worked so well that people and governments have been accepting, even relying on, Google’s “Integrity Check” shenanigans (and the Apple’s whatever analogue i-thing for iOS). The supply chain attacks that have been happening (from PyPi to AUR) feels like something that’s further pushing us to more centralized “authorities” who’ll then have absolute power over who can and who can’t pass.
Even if a truly independent entity were to come up with a full-fledged browser engine, as compatible as possible with current specs, Google still seems to possess lots of influence on the official Web standards and they can simply commit changes to the specs that would uncirvumventably require Google’s “blessing” to function (for your security, of course /s); so anything “not blessed” would simply fail to function because it isn’t signed by the “blessing”, “divine” keys.
And Mozilla doesn’t feel trustworthy as well, especially because they’re overly reliant on Google’s money to exist, and also because they’ve been pivoting to opt-out (so one must explicitly disable it and confirm their will to disable it, otherwise it will be on by default, which turns to be a shady lack of consenting, much like Google’s behavior) “features” much despite of their own userbase’s demands.
This said, I used to believe in third-way projects such as Servo and Ladybird… except the latter went down a very unacceptable road (founder turned out to be a transphobe who dismisses using neuter pronouns and assumes the user’s gender to be always a “he/him” because “we don’t do politics here”), and the former… it belongs to Linux Foundation, where big corps such as Microsoft, Google and Oracle have their horses (after all, “Microsoft loves Linux”; sure, Nadella, we know how Microsoft “loves” Linux /s).
I’m afraid there’s no light at the end of the fiber optics (pun intended) when it comes to alternative engines: either we try to actively boycott the “modern Web technologies” altogether (ditching HTTP(S) and pivoting to entire alternative protocols such as Geminiprotocol and Gopher whose standards/specs are slightly more distant from the dirty hands of “Google et al”; worth mentioning how Fediverse has Geminiprotocol-capable platforms such as tootik, it’s more doable than reinventing the cursed wheel of the Web which turns to be the infamous Chromium wheel) or we try to stick with the “lesser evil” (forks of Mozilla Firefox, until Firefox becomes totally enshittifiedly indistinguishable from Chromium) until a solution happens (or likely not, then we’re left with just the other path, which is pivoting to alternative standards altogether).