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...
When websites start blocking clients that don’t implement the wei handshake, you’ll be forced to use one that does if you want to visit those sites. Firefox will either adopt it or become a second rate browser.
I wish that this kind of thing would generate enough outrage to increase Firefox’ market share considerably (from the <3% it is today), and in that way deter websites from adopting it since they would block a larger share of users. Unfortunately, I think that might be too naive of me…
Most banking apps don’t work on rooted Android phones. It’s not the same, but I don’t think it’s a stretch to assume that at least these companies would force their customers to use specific software…
And I use my root to hide my root from my banking app… Idk about the implementation details of this, but I kinda think the same could happen here as well.
This is the problem for me. If my bank or other critical institution decides to refuse me access with Firefox, I can’t use Firefox. This is the crux of the issue. Google is creating a browser monopoly with it’s market dominance and attestation scheme.
MS tried to exert control in the early 2000’s with its IE dominance and was thwarted by an anti-trust lawsuit. Google will probably skate on this one. Nowadays the consumer is only a resource to be plundered. The customer is shit.
When websites start blocking clients that don’t implement the wei handshake, you’ll be forced to use one that does if you want to visit those sites. Firefox will either adopt it or become a second rate browser.
For now, Mozilla’s official stance is to oppose this proposal: https://github.com/mozilla/standards-positions/issues/852#issuecomment-1648820747
I wish that this kind of thing would generate enough outrage to increase Firefox’ market share considerably (from the <3% it is today), and in that way deter websites from adopting it since they would block a larger share of users. Unfortunately, I think that might be too naive of me…
You require Chrome or a Chromium based browser to view this comment.
Websites should be able to block me. I can just go elsewhere.
May be a bit problematic with banks, insurances and maybe government institutions…
it will truly be messed up if essential websites block user access because of this
Most banking apps don’t work on rooted Android phones. It’s not the same, but I don’t think it’s a stretch to assume that at least these companies would force their customers to use specific software…
And I use my root to hide my root from my banking app… Idk about the implementation details of this, but I kinda think the same could happen here as well.
This is the problem for me. If my bank or other critical institution decides to refuse me access with Firefox, I can’t use Firefox. This is the crux of the issue. Google is creating a browser monopoly with it’s market dominance and attestation scheme.
MS tried to exert control in the early 2000’s with its IE dominance and was thwarted by an anti-trust lawsuit. Google will probably skate on this one. Nowadays the consumer is only a resource to be plundered. The customer is shit.