Apple has deployed a system called Private Access Tokens that allows web servers to verify if a device is legitimate before granting access. This works by having the browser request a signed token from Apple proving the device is approved. While this currently has limited impact due to Safari’s market share, there are concerns that attestation systems restrict competition, user control, and innovation by only approving certain devices and software. Attestation could lead to approved providers tightening rules over time, blocking modified operating systems and browsers. While proponents argue for holdbacks to limit blocking, business pressures may make that infeasible and Google’s existing attestation does not do holdbacks. Fundamentally, attestation is seen as anti-competitive by potentially blocking competition between browsers and operating systems on the web.
Actually I like this.
All those people who’ve been trying to keep corporate technologies “open” were, in fact, working for the corporations to make people come to them. Most unknowingly, maybe. It’s just, well, litany of Gendlin case. You rely on corporate power, even if you are trying to hide it and talk about “open Web”.
The most important thing is that we take ideologically corporate technology where it’s not needed (there’s been plenty of hypertext systems in history, some kinda successful, and all that JS and AJAX stuff and various frameworks on top are so complex not because of any usefulness, but because of the corporate goal of backward compatibility, lumping everything together and even intentional complexity to cut off competition, and a single space).
We’d be just fine with a bunch of incompatible between themselves Hypercard-like things working over network. That’s what I think.
I really dislike Apple for what they’ve been in my somehow conscious years (born 1996), but things like Hypercard and Hotline (or KDX) from their older time seem to be just the right way to use personal computers.
Any single space with propaganda of “fragmentation being bad” is either not immune to what has happened to the Web, or already compromised.
I’m with you there, but that seems like a reason to fight
This would very likely be added to cloudflare by default (it would lower their costs), and that would put a solid chunk of the Internet behind the blackwall
Google mentioned these in their explainer (they don’t like that they’re fully masked): https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md#privacy-pass--private-access-tokens
Cloudflare explains them more too: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/
They are currently going through an IETF standardization: https://datatracker.ietf.org/wg/privacypass/about/
You can also read the architecture. In general I do trust Cloudflare more than Google. I have no doubt shitty sites won’t fall back to a captcha and will instead block access though, with either solution.
In general I do trust Cloudflare more than Google.
A large portion of the internet runs through Cloudflare’s network though, so IMO they’re just as much of a risk as Google.
However unlike Google, CloudFlare doesn’t have a history of killing off products just as users begin to adapt to them.
The main risk with Cloudflare is that if they think your device is malicious, it gets very hard to browse the internet, as every site hosted behind Cloudflare starts showing CAPTCHAs or rate limiting you. This could get worse if new APIs that determine if you’re legit don’t like you for whatever reason.
CF has only been public for a few years. Give it a decade and I’m sure they’ll be just as evil as Google.
That’s not why Google is harmful though - they’re harmful because almost all of their revenue comes from advertising - everything else they offer is just a funnel to gain data on the worlds population in order to better target advertising.
As for cloudflare - they showed their true colours last year with kiwifarms. They’ll happily host the worst websites in the world as long as they don’t get bad press.
Damn, didn’t know that, thanks for sharing!
Back to the days of using a different web browser for each website. I remember the acid test, IE 5.5, etc. Not fun as a user or web developer.
