floc
Our great sponsors
ads-privacy | floc | |
---|---|---|
16 | 92 | |
296 | 928 | |
1.4% | - | |
6.4 | 1.1 | |
about 1 month ago | about 1 year ago | |
Makefile | ||
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ads-privacy
-
If anything I've learned in marketing is that nobody knows anything except the algorithm - Another Performance Max post
Floc (not yet implemented): https://github.com/google/ads-privacy/blob/master/proposals/FLoC/FLOC-Whitepaper-Google.pdf
-
Firefox now blocks cross-site tracking by default in private browsing
Yeah, didn't word that right. They already do, but the flow of info will be reversed more or less. 3rd party data was where the money was made (still is but that's changing, which is what I'm getting at in general). Now sites generating first party data (which is less extensive - doesn't track your uid with PII across the web [generally speaking]) will be able to sell that data at a premium as 3rd party cookies die but 1st party cookies remain. and this all gets back to the FLoC api.
-
What will Happen to Google Display Ads in 2022?
Main solution for display remarketing will be the Federated Learning of Cohorts, the whitepaper is quite interesting
-
What is going on with "birds" names for the new generation of ad targeting technologies?
Why do Google's FLoC, TURTLEDOVE, Dovekey, Criteo's SPARROW, Magnite's PARRROT, NextRoll's TERN and Microsoft's PARAKEET all have similar bird-related names? This feels very cruel considering that in most cultures birds often symbolise freedom.
-
Google plans to stop targeting ads based on your browsing history
It's hard to fathom that statement coming from Google, a company that's built an empire by monetizing your browsing data. Looking forward, Temkin says the search giant is planning to use privacy-preserving APIs, like the "Federated Learning of Cohorts API" (FloC), to deliver relevant ads. That solution will rely on groups of users with similar interests, rather than drilling down to your specific behavior.
-
Google to stop selling ads based on your browsing history and drop cookies support for Chrome citing privacy concerns
They're aiming to implement what they called FLoC (Federated Learning of Cohorts) as a solution to avoid the need of third party cookies for ad trackers.Here's the whitepaper.
-
Google's article yesterday on new privacy practices. What exactly are the implications for Adwords?
That's going away, they will (supposedly) no longer have a profile that says TTFV is a golf lover or scotch drinker. But they will be put into a cohort and be targeted that way instead. I, admittedly, don't quite understand how this works, although the white paper seems like it could be helpful.
-
Google to Stop Selling Targeted Ads Based on Browsing History
"Instead, our web products will be powered by privacy-preserving APIs which prevent individual tracking while still delivering results for advertisers and publishers."
- The Federated Learning of Cohorts (FLoC) API is a privacy preserving mechanism proposed within the Chrome Privacy Sandbox. The goal of the FLoC API is to preserve interest based advertising, but to do so in a privacy-preserving manner.
floc
-
Google starts trialing its FLoC cookie alternative in Chrome.
Draft: https://github.com/WICG/floc
- Chrome vulnerability reported for 3.2 billion users
-
[D] Google FLoC and Topics API suspiciously similar.
"The browser uses machine learning algorithms to develop a cohort based on the sites that an individual visits. The algorithms might be based on the URLs of the visited sites, on the content of those pages, or other factors. The central idea is that these input features to the algorithm, including the web history, are kept local on the browser and are not uploaded elsewhere — the browser only exposes the generated cohort." Source: https://github.com/WICG/floc
-
Will a VPN help me? And is Kape Technologies ruining everything?
Google (or other third-party tracking) is also not effected by VPN. These groups use cookie syncing to assign you a unique ID and then collect this ID again as you browse the internet. That buyerID can then be cross-referenced (even with other buyerIDs) to generate all sorts of different demographic/psychographic information and used to fingerprint your online life for audience targeting. Google actually is in the works to take this a step forward with the FloC experiment. FloC (Federated League of Cohorts) actually deprecates the Set-Cookie header in favor of in-browser history scanning. Basically, in a year or two they plan to incorporate Chrome into their adtech stack and have it report your history/behavior to Google (regardless of whether you save history or not). Here is some good info on that: https://github.com/WICG/floc
-
Google Play Services now lets you delete your advertising ID when you opt out of ad personalization
Instead they propose new standards, like HTML Imports or FLoC, and the W3C decides as a whole whether or not they become official standards.
-
Google considers switching FLoC to a topic-based approach
With cross-site cookies, adnetwork.com has full information about what sites you've visited (among sites that incorporate their cookies). This isn't good either! But generally speaking, an individual site using adnetwork.com for advertising won't have or want access to that vector of your interests; many site operators don't even have visibility into what ads win real-time bidding, just that they're receiving money for providing their inventory. Certainly there are players that can provide demographic targeting metadata to site operators, but to my knowledge they are less widely known and certainly not cheap, and I imagine (or hope) any players with wide enough cookie reach would be discouraged from maintaining a database that could associate metadata with PII.
With FLoC, though, the idea was that the browser would provide document.interestCohort() and the individual site's JS could react accordingly: https://github.com/WICG/floc . This means that any site, regardless of its contracts with ad networks, could immediately identify your cohort and associate it with your activity. Web developers working in good faith would be encouraged to have user.cohort or user.topic fields from day one "just so you have it" - imagine all the ways someone could use this in bad faith. Inevitably this data would leak (or be intentionally leaked) and could trivially become a target list for doxxing closeted people. It's a dangerous, dangerous proposal.
-
Trying to understand Addressability (for native mobile, and in general)
You can't find any info about this because there isn't really any. Josh Karlin, who is the maintainer of the FLoC working document, said at an event that it might make sense to swap to topics. It's essentially just reducing the entropy of the cohorts and giving them a more comprehensible (and probably less useful) taxonomy. That's all the info there is.
-
Apple's Plan to "Think Different" About Encryption Opens a Backdoor to Your Private Life
https://github.com/WICG/floc explains the overall goals.
- Firefox Users Continue to Decrease Despite Proton Update
-
Amazon is blocking Google’s FLoC
It's pretty complicated and my understanding could be wrong and definitely not an expert. All the stupid CIA-style names that keep changing don't help. Turtledove, fledge, sparrow lol.
But from what I think I know that's kind of right technically, but kind of not in terms of actual real privacy.
Yes, the actual browsing data, e.g. for the basic floc cohorts only what amazon product page you visited, is no longer 'sent' to ad networks (that's a pretty big oversimplification of how ad networks track you but for brevity). That data is parsed in your browser to generate a cohort ID for you.
But this cohort ID is exposed to the world document.interestCohort() and is what's used for targeting and tracking.
To me it seems that the cohorts are so small "thousands of people" + IP or UA it's basically the same as a semi-long lasting uuid.
Here's an image from google's site.
https://web-dev.imgix.net/image/80mq7dk16vVEg8BBhsVe42n6zn82...
It also seems like Chrome/google might be still defaulting browser settings to give themselves even more data just like they currently do?
https://github.com/WICG/floc#qualifying-users-for-whom-a-coh...
BUT when you layer on the other proposals (Fledge/Turtledove/Dovekey or whatever) - which I don't understand that much maybe someone else can explain - it seems like it basically collect this page/product level data and makes it available to DSP etc for tracking/ad serving (again if not technically 1:1 basically in consequence given the sizes of these groups).
Like one of the proposals talks about a 'trusted' key/value server which doesn't seem that different from what already happens? The original proposal wanted to move the entire ad bid/target/serve process into the browser.
What are some alternatives?
ip-blindness
bypass-paywalls-chrome - Bypass Paywalls web browser extension for Chrome and Firefox.
turtledove - TURTLEDOVE
ungoogled-chromium-archlinux - Arch Linux packaging for ungoogled-chromium
vanced-website-v2 - Source Code of the Vanced Website
uBlock - uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
privacytools.io - 🛡🛠 You are being watched. Protect your privacy against global mass surveillance.
chromium - The official GitHub mirror of the Chromium source
Firefox-UI-Fix - 🦊 I respect proton UI and aim to improve it.
AmIUnique - Learn how identifiable you are on the Internet
identity-gatekeeper
brave-browser - Brave browser for Android, iOS, Linux, macOS, Windows.