This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Why would they? It’s FrEE maRKeT. Google can point to Edge and Safari as proof that they don’t have a monopoly on browsers, so no anti-trust issue there no sireee. The fact that Edge is based on Chromium does not factor into this (in fact the EU loves it, just look at what they did to “liberalize” the electricity market, aside from some extremely anecdotal stories, it’s all companies whose only job is to build a website and the fiscal “infrastructure” to buy energy from state-controlled producers to resell it at a markup using state-controlled energy distributors, but hey there is a private middleman so it’s liberal and the innovation/investment dividends will pay out any year now… any year…).
The concept of the WWW being supported by free, standard, interoperable protocols was never codified into law. Despite how much good it has done so many industries to have a common free interoperable tech stack, it doesn’t have to be this way; the French Minitel was a walled garden built by France Telecom, and that was 100% legal, because interoperability is not a legal requirement. The Apple Store and Game Consoles work under the same principle, you basically can’t sell anything on there without abiding by some asinine rules (Apple has had some issues but IIRC that has to do with them abusing their monopoly position to extract 30 % of all sales, not with the fact that they have an exclusive App Store to begin with).
Also this whole bullshit is not new and was never legally challenged because there is no case. For years you could not even browse instagram in your browser because they “only supported the mobile app”, which was a blatant way to force you into a walled garden where they can force you to watch as many ads as they want and where scraping is much harder.
Brave is built on Chromium. So, by default, no they are not safe from this. Without extra effort, Brave will have this feature. I don’t know if its feasible but there’s a chance the Brave devs can remove the code from their distribution, but that’s the best case scenario and just puts them in the same position as Firefox: they get locked out because they refuse to implement the spec.
It may be dead to its users anyway depending on how forceful Google is with this. If Brave doesn’t work on 98.8% of all websites with advertising or indeed on 49.5% of all websites (approximately Google’s ad network’s reach), it becomes as niche as lynx.
I’ll keep using Firefox and be extremely vocal about websites that won’t support it. I mean that’s all I can really do.
And hope the EU will oppose it.
Why would they? It’s FrEE maRKeT. Google can point to Edge and Safari as proof that they don’t have a monopoly on browsers, so no anti-trust issue there no sireee. The fact that Edge is based on Chromium does not factor into this (in fact the EU loves it, just look at what they did to “liberalize” the electricity market, aside from some extremely anecdotal stories, it’s all companies whose only job is to build a website and the fiscal “infrastructure” to buy energy from state-controlled producers to resell it at a markup using state-controlled energy distributors, but hey there is a private middleman so it’s liberal and the innovation/investment dividends will pay out any year now… any year…).
The concept of the WWW being supported by free, standard, interoperable protocols was never codified into law. Despite how much good it has done so many industries to have a common free interoperable tech stack, it doesn’t have to be this way; the French Minitel was a walled garden built by France Telecom, and that was 100% legal, because interoperability is not a legal requirement. The Apple Store and Game Consoles work under the same principle, you basically can’t sell anything on there without abiding by some asinine rules (Apple has had some issues but IIRC that has to do with them abusing their monopoly position to extract 30 % of all sales, not with the fact that they have an exclusive App Store to begin with).
Also this whole bullshit is not new and was never legally challenged because there is no case. For years you could not even browse instagram in your browser because they “only supported the mobile app”, which was a blatant way to force you into a walled garden where they can force you to watch as many ads as they want and where scraping is much harder.
Is Brave safe from these shenanigans? Asking for a friend.
Brave is built on Chromium. So, by default, no they are not safe from this. Without extra effort, Brave will have this feature. I don’t know if its feasible but there’s a chance the Brave devs can remove the code from their distribution, but that’s the best case scenario and just puts them in the same position as Firefox: they get locked out because they refuse to implement the spec.
I have to imagine they will strip it because if they don’t, it’ll be dead to all of their users.
It may be dead to its users anyway depending on how forceful Google is with this. If Brave doesn’t work on 98.8% of all websites with advertising or indeed on 49.5% of all websites (approximately Google’s ad network’s reach), it becomes as niche as lynx.