The submitted title was "WordPress Proposal to Treat Google's FLoC as a Security Concern". That makes it sound like Wordpress itself is officially making this proposal. Is it? The page doesn't look like that to me. We've reverted the title in keeping with the site rule: " Please use the original title, unless it is misleading or linkbait; don't editorialize. " ( https://news.ycombinator.com/newsguidelines.html ).
The page does seem to be the official wordpress development blog, linked from wordpress.org's "get involved" page. "The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate."
Proposal: Treat FLoC as a security concern
81–90 of 274 posts
Re: Proposal: Treat FLoC as a security concern
#82I just love the Google's way of thinking. Users: We hate cookies, because they are abused to hurt our privacy by allowing advertisers to build a profile about us Google: We have a great idea! We can get rid of 3rd party cookies and instead make your browser build profile about you and share it with everyone.
IIUC while floc does indeed build a profile browser side it isn’t something that advertisers can track with the same precision as they can with 3p cookies. So while it’s not the holy grail it does appear to be a small step in the right direction from the status quo. Do I understand the situation correctly? Genuinely curious.
Re: Proposal: Treat FLoC as a security concern
#83Re: Proposal: Treat FLoC as a security concern
#84Can't privacy concious browser defeat FLoC simply by sending random cohort IDs on each request?
I would believe that random noise is easy to filter when you are Google.
Re: Proposal: Treat FLoC as a security concern
#85disclosure: I don't know what FLoC is, and the OP page doesn't load. Seems to be something about web ads security.
Re: Proposal: Treat FLoC as a security concern
#86Earlier quoted context omitted.
Possibly GDPR? As an explicit no-consent to tracking? Not rhethorical questions, I know too little about the details.
When you use Chrome for the first time, it makes you accept its ToS which tells you they are going to track you.
Re: Proposal: Treat FLoC as a security concern
#87The submitted title was "WordPress Proposal to Treat Google's FLoC as a Security Concern". That makes it sound like Wordpress itself is officially making this proposal. Is it? The page doesn't look like that to me. We've reverted the title in keeping with the site rule: " Please use the original title, unless it is misleading or linkbait; don't editorialize. " ( https://news.ycombinator.com/newsguidelines.html ).
Seems like it is to me.
Re: Proposal: Treat FLoC as a security concern
#88Lately the loss of security, increased tracking, etc are very pressing issues, which the "general public" is not aware of. Would it be feasible, or actually doable, to create an wareness month - a la Movember? This would help to shine some light on what is being done by major corporations, and which affects everyone.
Re: Proposal: Treat FLoC as a security concern
#89I just love the Google's way of thinking. Users: We hate cookies, because they are abused to hurt our privacy by allowing advertisers to build a profile about us Google: We have a great idea! We can get rid of 3rd party cookies and instead make your browser build profile about you and share it with everyone.
IIUC while floc does indeed build a profile browser side it isn’t something that advertisers can track with the same precision as they can with 3p cookies. So while it’s not the holy grail it does appear to be a small step in the right direction from the status quo. Do I understand the situation correctly? Genuinely curious.
Re: Proposal: Treat FLoC as a security concern
#90Earlier quoted context omitted.
When you use Chrome for the first time, it makes you accept its ToS which tells you they are going to track you.
They will lose that case under GDPR, you can't hide the details in ToS and hope the user doesn't see it. You must get informed and freely given consent. Google is violating both, because I can't click "No" and the information is so hidden you can't expect a normal consumer to find it. It will take a few years but they're going to get hit very very hard by EU privacy regulators.