WordPress Proposal to Treat Google's FLoC as a Security Concern

• floc

  92 928 1.1 Makefile

  Discontinued This proposal has been replaced by the Topics API.

  

It's sort of opt-in.

For websites, FLoC cohort computation only triggers 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 Chrome history data sync, must not block third-party cookies, must have enabled Google web activity tracking and must have enabled ad personalization. (https://github.com/WICG/floc#qualifying-users-for-whom-a-coh...)

Also, you can disable FLoC via chrome://settings/privacy or chrome://flags. (https://github.com/WICG/floc/issues/103#issuecomment-8218146...)

It's not a perfect opt-in, but it's also not malware.

• privacy-preserving-ads

  8 93 5.9

  Privacy-Preserving Ads

  

Chrome is not the only browser working on more advertising-specific APIs as more-private replacements for third-party cookies. For example, Edge is proposing PARAKEET [1] for remarketing, and Safari has implemented an initial conversion tracking API [2].

[1] https://github.com/WICG/privacy-preserving-ads/blob/main/Par...

[2] https://webkit.org/blog/8943/privacy-preserving-ad-click-att...

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project