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:
Source.
https://datatracker.ietf.org/doc/html/draft-ietf-ppm-dap#name-security-considerations
The explicitly say if the aggregator is controlled by hostile party, and in my scenario that would be Mozilla, they could have full access to the deanonymized data. It’s out of scope for their protocol.
And while the DAP draft is nice, it doesn’t change my threat model, it just introduces extra steps. As the absolute hunger of AI inputs for models have shown us, if a company has the capability to get data, they will. Mozilla has demonstrated they are hungry for data and money. I don’t want to give them the capability