9 ms·
> When it comes to things like FLoC (now Topics) [1] the privacy implications of having an agile standards board are more important than ever, and may actually
by atomicUpdate 4y ago
> When it comes to things like FLoC (now Topics) [1] the privacy implications of having an agile standards board are more important than ever, and may actually have significant impacts on people's physical safety.
This sounds like needless fear-mongering. Is there anything to backup any concerns about people's physical safety?
- darig 4y ago[dead]
- btown 4y agoDon't take my word for it: WordPress treated FLoC as a security concern in 2021: https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/ https://make.wordpress.org/core/2021/04/18/proposal-treat-fl... A good overview of the context: https://digiday.com/media/we-cant-un-floc-ourselves-googles-cookieless-ad-targeting-proposal-under-fire-from-ethics-researchers-lawmakers-for-discriminatory-potential/ https://digiday.com/media/we-cant-un-floc-ourselves-googles-... More detail: https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-... When it comes to Topics, it's essential that there be hands on the wheel at W3C that approach the solidification of e.g. the Topics taxonomy https://github.com/patcg-individual-drafts/topics/blob/main/taxonomy_v1.md https://github.com/patcg-individual-drafts/topics/blob/main/... from a neutral perspective that takes into account the various ways in which proposed topics could be dangerous, and how strongly to word the specification to prevent it from creeping in increasingly privacy-eroding ways in the future.