Hacker GitHub

← All repos

WICG/floc

View on GitHub ↗ ★ 928 Makefile archived

This proposal has been replaced by the Topics API.

70 mentions on Hacker News by 44 people: 3 stories, 67 comments · first 2019-08-22 · latest 2021-08-17

Mentions per year 70 mentions · busiest year 2021 (60)
20082026
  1. …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…
  2. …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…
    comment by dillondoyle · 2021-06-15 · in Amazon is blocking Google’s FLoC
  3. …browser support. This is the path FLoC is following: it's currently incubated under the WICG ( https://github.com/WICG/floc ) and Chrome is developing it. Other browsers are paying attention and evaluating: that's what this Mozilla article…
    comment by jefftk · 2021-06-11 · in Privacy Analysis of FLoC
  4. FLoC as a source of fingerprinting bits has been an issue in W3C discussions of the project. https://github.com/WICG/floc/issues/69 As a fingerprinting surface FLoC has similar properties to the Battery Status API -- not stable for the…
  5. …an Economist reader a week later on a different website. If FLoC works, you can still do that. https://github.com/WICG/floc won't really let advertisers do that, this is what https://github.com/WICG/turtledove is for (Disclosure: I work on…
    comment by jefftk · 2021-06-01 · in Apple, FedEx and the cookie apocalypse
  6. …the credibility of the field. The issue is that the replacement that are currently in the works ( https://github.com/WICG/floc and https://github.com/WICG/turtledove/blob/main/FLEDGE.md ) are extremely complex, will still dramatically…
  7. …that the user visits when not in incognito mode will be included in the POC cohort calculation. https://github.com/WICG/floc#sites-which-interest-cohorts-wi... This sounds to me like all sites, whether they contain ads are not, are used to…
  8. They seem to be aware of this https://github.com/WICG/floc#excluding-sensitive-categories I haven't seen details of how they expect this to actually work though.
  9. …many disparate groups[1]. [0] https://www.theverge.com/2021/3/3/22310332/google-privacy-re... [1] https://github.com/WICG/floc/issues/100
  10. FYI, if you are like me that has no idea what FLoC is until now, please see: https://github.com/WICG/floc
  11. …Nginx: add_header Permissions-Policy interest-cohort=(); [1] https://github.com/WICG/floc#opting-out-of-computation
  12. …= await document.interestCohort(); Seems pretty easy to override with a simple extension. [0] https://github.com/WICG/floc
    comment by ehsankia · 2021-04-21 · in Everybody Hates “FLoC”
  13. …if you call the document.interestCohort API or load ads - these actions are considered an opt-in. ( https://github.com/WICG/floc/issues/103 ) For users, it's sort of opt-in, too: You must be logged into a Google account, must have enabled…
    comment by mark_and_sweep · 2021-04-19 · in Proposal: Treat FLoC as a security concern
  14. I think you can enable/disable FLoC via chrome://settings/privacy or chrome://flags. See: https://github.com/WICG/floc/issues/103#issuecomment-8218146... Then again, FLoC is only enabled "in a limited set of circumstances" anyways. For…
    comment by mark_and_sweep · 2021-04-19 · in Proposal: Treat FLoC as a security concern
  15. Yes. Take a look at this issue: https://github.com/WICG/floc/issues/103 Then again: "final design is still subject to change based on [Origin Trial] feedback".
    comment by mark_and_sweep · 2021-04-19 · in Proposal: Treat FLoC as a security concern
  16. I've not been following this proposal closely I did find https://github.com/WICG/floc >Tracking people via their cohort >A cohort could be used as a user identifier. It may not have enough bits of information to individually identify…
  17. …you can only make it so difficult that it isn't worth doing it but not impossible to do): https://github.com/WICG/floc/issues/100
  18. …(or not having ads on the page during the trial) is the same as opting out. But then on https://github.com/WICG/floc#opting-out-of-computation > A site should be able to declare that it does not want to be included in the user's list of…
  19. …is a more privacy-friendly alternative to third-party cookies is deeply flawed, please read [this]( https://github.com/WICG/floc/issues/100 ).
    comment by livre · 2021-04-16 · in Nobody is joining Google's FLoC
  20. …themselves This does not work, `http-equiv` does not work for `Permissions-Policy`.[1] * * * [1] https://github.com/WICG/floc/pull/47#issuecomment-786966847
  21. …segments for itself, FLoC is a web standard, so third-parties can de-anonymize as a side-effect: https://github.com/WICG/floc/issues/100 Frankly the same problem exists in PCM’s, Apple’s proposed solution to allow private tracking from ad…
    comment by lstamour · 2021-04-16 · in FLoC Away from Chrome
  22. …might be based on the URLs of the visited sites, on the content of those pages, or other factors. https://github.com/WICG/floc
    comment by est31 · 2021-04-16 · in FLoC Away from Chrome
  23. …was a github issue, but only containing a request for such a header, not actually describing one. https://github.com/WICG/floc/issues/13 So I understand it correctly, currently publishers can't opt out from this tracking? What if you…
    comment by est31 · 2021-04-16 · in FLoC Away from Chrome
  24. https://github.com/WICG/floc/issues/82 >During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page load ads or ads-related resources. Who's to say how this evolves in the future?
  25. Note the suggestion they are looking into, making sites "sticky": https://github.com/WICG/floc/commit/d822a35f4bfe7d5003fda4a7... Although the follow-up comment summarizes why this probably won't work https://github.com/WICG/floc/commit/d82…
  26. …a cohort for my task, vs just being anonymous. EDIT: that would appear to be TURTLEDOVE [1] [0] https://github.com/WICG/floc [1] https://github.com/WICG/turtledove The FloC announcement is https://blog.google/products/ads-commerce/2021-01-p…
  27. …already mention this: > Whether the browser sends a real FLoC or a random one is user controllable https://github.com/WICG/floc
  28. …mode it's recommended that browsers just throw an exception rather than provide fake data: https://github.com/WICG/floc/blob/dcd4c042fa6a81b048e04a78b1...
  29. …precomputed? The explainer indicates it's a Promise: "cohort = await document.interestCohort()" -- https://github.com/WICG/floc One reason to make it async could be to give browsers the option to gate access behind a permissions prompt in…
    comment by jefftk · 2021-04-12 · in Brave disables Chromium FLoC features
  30. …ones who can use FLOC It is available to everyone: cohort = await document.interestCohort(); See https://github.com/WICG/floc (Disclosure: I work for Google, speaking only for myself)
    comment by jefftk · 2021-04-11 · in Brave disables Chromium FLoC features
  31. From the README.md at https://github.com/WICG/floc : "This API democratizes access to some information about an individual's general browsing history (and thus, general interests) to any site that opts into it . This is in contrast to…
    comment by 1vuio0pswjnm7 · 2021-04-10 · in Brave disables Chromium FLoC features
  32. …entirely agree. It doesn't change often enough, leading to easy fingerprinting scenarios[1]. 1. https://github.com/WICG/floc/issues/4
    comment by Sephr · 2021-04-10 · in Brave disables Chromium FLoC features
  33. …about that [1] and here's an EFF article about why it's dangerous [2]. [0] https://brave.com/ [1] https://github.com/WICG/floc [2] https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-...
    comment by mcrittenden · 2021-04-10 · in Brave disables Chromium FLoC features
  34. For those who like me wonder what is FLoC : https://github.com/WICG/floc
  35. …cohort calculation by sending the HTTP response header: Permissions-Policy: interest-cohort=()" https://github.com/WICG/floc Added to proxy config. http-response add-header "Permissions-Policy: interest-cohort=()"
    comment by 1vuio0pswjnm7 · 2021-04-10 · in Am I FLoCed?
  36. …this yourself if you use common user firewall tools such as LittleSnitch/LuLu/OpenSnitch/etc. [0] https://github.com/WICG/floc#qualifying-users-for-whom-a-coh...
  37. …would sell to advertisers: the proposal is that it be available to all JavaScript in the browser: https://github.com/WICG/floc What you get in return is that ad-supported sites you visit are better funded because they can show…
    comment by jefftk · 2021-03-05 · in Google’s FLoC Is a Terrible Idea
  38. > they have to show me they have nothing up their sleeve first https://github.com/WICG/floc describes something open source and running on the client. Will that be sufficient, or is there additional disclosure you'd like to see?
    comment by jefftk · 2021-03-05 · in Google’s FLoC Is a Terrible Idea
  39. Yes: https://github.com/WICG/floc > "Whether the browser sends a real FLoC or a random one is user controllable." FLoC stuff is client side. You can send nil FLoC IDs. You can randomize them on every request. You can swap them with your…
    comment by darren_ · 2021-03-04 · in Google’s FLoC Is a Terrible Idea
  40. You'll still be tracked by advertisers using FLoC https://github.com/WICG/floc https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-...
  41. …the API) will decide. The proposal is not that far along yet. You could consider filing an issue at https://github.com/WICG/floc/issues > You suggest that the code is in the browser (which i doubt - its certainly not at the moment!)…
  42. …a browser vendor send down a mapping of cohort hashes to interest vectors? I don't see anything in https://github.com/WICG/floc that suggests that couldn't happen, and it seems like it could greatly enhance utility without too much…
  43. See https://github.com/WICG/floc > Is it be possible to disable? "A site should be able to declare that it does not want to be included in the user's list of sites for cohort calculation. This can be accomplished via a new interest-cohort…
  44. …how many cohorts can a person be part of? It's just: cohort = await document.interestCohort(); See https://github.com/WICG/floc (Disclosure: I work on ads at Google, speaking only for myself.)
  45. …of them. No, users are only in a single cohort: "cohort = await document.interestCohort()" -- https://github.com/WICG/floc (Disclosure: I work on ads at Google, speaking only for myself)
  46. …you can do whatever. (‘Whether the browser sends a real FLoC or a random one is user controllable’ https://github.com/WICG/floc )
  47. …headphones for the next 3 weeks whenever I pull up a weather report The WSJ seems to be describing https://github.com/WICG/floc , but the kind of remarketing you're describing is what https://github.com/WICG/turtledove is intended to…
  48. …The bit you're quoting sounds like the WSJ trying to describe https://github.com/WICG/floc . That depends on the browser choosing to support the API, yes. (Disclosure: I work on ads at Google, speaking only for myself)
  49. …against people’s general interests I have to wonder if the double meaning here was intentional. [0] https://github.com/WICG/floc
  50. …like your post. It does conflate Privacy Sandbox with one of the specific proposals, however: [...] https://github.com/WICG/floc Thanks for the clarification Jeff. > Another component of Privacy Sandbox is Turtledove (…