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...
Unfortunately when my bank or other critical institution rejects Firefox for failure to use attestation, I can’t even do that. I’ll be forced to use Chrome. Firefox would have to adopt WEI to remain compatible. In that case I can use Firefox, but it would be the same as using Chrome.
I’d say the monopoly Google has with Chrome is way more threatening than in the early 2000’s with MS and IE. That threat resulted in an anti-trust lawsuit, but not a peep from any government about the destruction Google is doing.
I‘m old so i actually remember this but I‘m old so my memory might be shit but wasn‘t the lawsuit about the fact that microsoft shipped IE wirth windows as a default browser and not about it being too dominant?
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.
No brave users don‘t care. Brave proved how untrustworthy they are and in any case their business model is unethical yet they still have a cult like following plus a group of crypto bros that are obsessed with getting digital pennies.
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.
Unfortunately when my bank or other critical institution rejects Firefox for failure to use attestation, I can’t even do that. I’ll be forced to use Chrome. Firefox would have to adopt WEI to remain compatible. In that case I can use Firefox, but it would be the same as using Chrome.
I’d say the monopoly Google has with Chrome is way more threatening than in the early 2000’s with MS and IE. That threat resulted in an anti-trust lawsuit, but not a peep from any government about the destruction Google is doing.
I‘m old so i actually remember this but I‘m old so my memory might be shit but wasn‘t the lawsuit about the fact that microsoft shipped IE wirth windows as a default browser and not about it being too dominant?
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.
No brave users don‘t care. Brave proved how untrustworthy they are and in any case their business model is unethical yet they still have a cult like following plus a group of crypto bros that are obsessed with getting digital pennies.