In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
Additional Resources:
The proposal’s explainer dances around the fact that it can be used for that.
Combine them and you have an anti-adblocking feature.
It also says
Which is a whole lot of nothing. Of course you can still install extensions and sure, it can still request attestation, but that doesn’t mean it will get it. But this isn’t even important because I’m sure attestation for being a human (case 1) will fail anyway if the ads get blocked.
But even assuming that it doesn’t interfere with ad blockers, this is still going to allow some shitty website to query code running on your device that isn’t under your control to snitch on you. It’s fundamentally stupid and wrong to trust any client data about the client, using extra processors and features is a garbage, intrusive workaround that still doesn’t even actually work reliably from the shitty developers/website owner’s point of view. Also see: Android custom ROMs and the lengths they successfully go to in order to run banking apps.
And the second and forth points are already solved using client certificates.