(no title)
adamsvystun | 4 years ago
If you literally look up the most upvoted HN article about FLoC [1], it specifies two main issues with FLoC in BOLD: Fingerprinting and Cross-context exposure. Which if I understand correctly the Topics API fixes. But the article implies that these are minor problems that we never really cared that much about.
Whether it is this or constant aggressive writing, it seems that the goal of this blog post is to simply inspire anger and hate, while not furthering the discussion on the topic. Which makes this article unhelpful (if not damaging) to the goal of personal data privacy.
[1] https://news.ycombinator.com/item?id=26344013 [2] https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-...
xg15|4 years ago
However I think the article is right in the sense that we shouldn't miss the forest for the trees. Image you were robbed and the robber suddenly asked if your issue with him could be solved if he only took half of what's in your wallet. Surely that would be an improvement but it doesn't solve the root issue of him robbing you in the first place.
In the same sense, I think pulling attention back to the fact that Google is building third-party tracking right into the browser - and also aggressively protecting the whole concept of tracking as some sort of fundamental necessity of the web - is justified.
throwawaythekey|4 years ago
The pejorative robbed is doing a lot of heavy lifting here. Advertising is how users pay for free services. Making the form of payment more agreeable is a worthwhile goal.
As full disclosure I earn a living in the advertising ecosystem. Any feature that means stakeholders stop asking me to invent backdoor fingerprinting and correlate against data obtained from shady brokers is a welcome step in my opinion.
hackerfromthefu|4 years ago
The blog post makes sensible points identifying Google's PR based response. Thus your ad hominem attack on the blog instead of the content makes me wonder if you have conflicts of interest regarding this topic?
sva_|4 years ago
There isn't much to discuss, I would think. This is an extremely user-hostile feature to be implemented in the clients (browsers) which comes with a lot of downsides, and absolutely no benefit to the user. I don't know how detached people at Google must be to consider this okay, or to think that any of the privacy-focused browsers would join in on this.
hackerfromthefu|4 years ago
unknown|4 years ago
[deleted]