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...
Wow they moved incredibly fast, even considering the repository was first committed to in April 2023. I wonder why the outrage only started a few days ago? There was also a discussion, started in May.
It’s a shame that no matter the amount of outrage, no matter what the pitfalls of this change may be, it’s going to happen no matter what because money.
If you switch to a browser that cannot be remotely attested, eventually commercial websites will just stop serving you. So switch now and tell everyone you know to switch to something that is not Chrome or Safari.
Safari already does this in the form of Personal Access Tokens, and the reason the web hasn’t taken it and ran with it yet is because their market share is ~20%. Chrome is 70%. This is about to be a systemic problem that you cannot fix by switching to software that respects your freedom.
From what I read in the related links they only claim to have applied pressure, they didn’t cave because of that pressure though. Again it seemed to be about money.
“The only saving grace was Vista’s very painful and long development period where Palladium was eventually killed so Vista could actually ship.”
Wow they moved incredibly fast, even considering the repository was first committed to in April 2023. I wonder why the outrage only started a few days ago? There was also a discussion, started in May.
It’s a shame that no matter the amount of outrage, no matter what the pitfalls of this change may be, it’s going to happen no matter what because money.
Luckily we have choices. From WebKit browsers to Mozilla browsers. This will make me quit chrome. (Way overdue anyways)
If you switch to a browser that cannot be remotely attested, eventually commercial websites will just stop serving you. So switch now and tell everyone you know to switch to something that is not Chrome or Safari.
Safari already does this in the form of Personal Access Tokens, and the reason the web hasn’t taken it and ran with it yet is because their market share is ~20%. Chrome is 70%. This is about to be a systemic problem that you cannot fix by switching to software that respects your freedom.
Well, I don’t know about now, but this Microsoft employee says some time ago an outrage worked.
From what I read in the related links they only claim to have applied pressure, they didn’t cave because of that pressure though. Again it seemed to be about money.
“The only saving grace was Vista’s very painful and long development period where Palladium was eventually killed so Vista could actually ship.”
Right, so outrage that they couldn’t get enough money.
We also cannot say it wasn’t a factor in their decision.
but we also have no reason to either