"No shady privacy policies or back doors for advertisers" proclaims the Firefox homepage, but that's no longer true in Firefox 128.
Less than a month after acquiring the AdTech company Anonym, Mozilla has added special software co-authored by Meta and built for the advertising industry directly to the latest release
From my understanding of their implementation, you have to give a Mozilla server all of your traffic history, and then they feed a curated, sanitize topic list of that activity to the advertisers.
So now we’re trusting Mozilla with your full browsing history, that seems like a really bad idea. Even if I love and trust Mozilla, I don’t want to add yet another thing to the critical path
All your data is encrypted on our servers so we can’t read it – only you can access it. We don’t sell your info to advertisers because that would go against our data privacy promise.
PPA does not involve sending information about your browsing activities to anyone. This includes Mozilla and our DAP partner (ISRG). Advertisers only receive aggregate information that answers basic questions about the effectiveness of their advertising.
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
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:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
From my understanding of their implementation, you have to give a Mozilla server all of your traffic history, and then they feed a curated, sanitize topic list of that activity to the advertisers.
So now we’re trusting Mozilla with your full browsing history, that seems like a really bad idea. Even if I love and trust Mozilla, I don’t want to add yet another thing to the critical path
https://support.mozilla.org/en-US/kb/privacy-preserving-attribution
https://hackertalks.com/comment/4359282
How are they different from any other VPN service or even uBlock? They all have access to your browsing info and can potentially use it for profit.
https://www.privacyguides.org/en/basics/vpn-overview/
You think I don’t know how a VPN works?
I think you misunderstood what I meant.
If you have syncing on, you are already trusting Mozilla with your history.
deleted by creator
You are correct. My mistake.
https://www.mozilla.org/en-US/firefox/features/sync/
Oh yeah, agreed, if your syncing then your security model doesn’t include worrying about tracking.
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