Live data from Hacker News

WebKit Tracking Prevention Policy

webkit.org

201–210 of 254 posts

Re: WebKit Tracking Prevention Policy

#201
post #40

So what is going to happen when Apple succeeds in making it impossible to make any money off advertisements shown to iOS users on the web? I'm currently imagining a future where publishers start to just redirect iOS traffic to install their app, where they can actually make money. Good news for the walled garden, I guess?

The same thing that happens as more people install ad blockers.

Re: WebKit Tracking Prevention Policy

#202
post #64
post #47

Earlier quoted context omitted.

Didn't people make money off internet advertising before the modern surveillance-marketing complex? What happened to it? I mean, maybe the answer is that those ads were only profitable because of the novelty factor and now that we have metrics we know they don't work, or at least don't work anywhere close to how much they cost. But I do miss things like the webcomics running their own ad network, Google's textual ads…

> Didn't people make money off internet advertising before the modern surveillance-marketing complex? What happened to it? Non-contextual advertising still exists, but it's perceived as less effective, so there's a lot less money in it. I don't know if that perception is correct, but I do remember back when a common complaint from people was that the ads they saw weren't relevant to them. It's also not just targeted…

If I am reading Daring Fireball - list ad price $6500 a week for an ad at the beginning of the week and a thank you at the end of the week - doesn’t that automatically tell you something about me?

Re: WebKit Tracking Prevention Policy

#203

Earlier quoted context omitted.

How is fraud handled for TV advertising? Or print? This isn’t some weird new problem. The truth is that ad-tech wants to track you to make your profile more valuable, however, a less valuable user doesn’t mean advertising doesn’t work, it just means the bottom-feeding middlemen get a less profound payday. Why not just flip the model from eyeballs and clicks to actual ad effectiveness? Newspaper car ads have this down…

if you are a publisher and have actual content humans care about, ditch the ad networks and start selling your pixels directly to relevant advertisers. Good luck with direct ad sales, unless you are a large company with a large ad sales team and correspondingly large budget.

John Gruber’s Daring Fireball and a few other sites seem to be doing okay without a large sales team. He is a one man company.

Re: WebKit Tracking Prevention Policy

#204
post #194

Earlier quoted context omitted.

I don't think we'd in practice see people lying one way or the other about a particular name level being "public". If GitHub wants to track people across all *.github.io pages, it can, trivially. It controls the infrastructure, after all.

> If GitHub wants to track people across all .github.io pages, it can, trivially. It controls the infrastructure, after all.* If WebKit fully implements what they're describing here then GitHub should not be able to use their control of *.github.io to track people across those pages.

quotemstr was talking about the infrastructure that they control. It's true that they can track visitors server-side if they want to.

Re: WebKit Tracking Prevention Policy

#205
post #126
post #9

Earlier quoted context omitted.

We're willing to do specifically targeted mitigations, but only if we have to. So far, nearly everything we've done has been universal or algorithmic. The one exception I know of was to delete tracking data that had already been planted by known circumventers, at the same time as the mitigation to stop anyone else from using that particular hole (HTTPS super cookies). This is in contrast to Mozilla and Edge tracking…

Thank you for doing this work. I don’t know what effect it has on Apple as a whole but for customers like me it reinforces my loyalty to Apple.

Totally true. Thanks.

Re: WebKit Tracking Prevention Policy

#206
post #157
post #148

A first party is a website that a user is intentionally and knowingly visiting, as displayed by the URL field of the browser, and the set of resources on the web operated by the same organization. In practice, we consider resources to belong to the same party if they are part of the same registrable domain: a public suffix plus one additional label. Example: site.example, www.site.example, and s.u.b.site.example are…

We have mixed feelings about this. Most people could probably figure out that google.com and google.co.uk are owned by the same entity. And probably many people are aware that youtube.com and google.com are related. But some entities own hundreds of domain names with no clear lexical relationship. I doubt a lot of people would expect TechCrunch.com and huffpost.com to be related and would not really expect to be trac…

"We have mixed feelings about this."

No need.

Anyone choosing to mix and match also has the resources for some minor duplication of effort.

Or they could just do it all service side.

Re: WebKit Tracking Prevention Policy

#207
post #179
post #173

Earlier quoted context omitted.

That's a very interesting point. But tracking-free services won't really have a major mindshare with the general public because you really can't compete with "free." And there's nothing preventing Google from leveraging Youtube/Gmail/Search to push out other browsers which have tracking protection. Youtube already plays less well with Firefox. Gmail isn't exactly snappy on Safari either.

Yes, competing with Google is still a main challenge. Still, Apple seems to be managing by providing the browser for free as a value-add when you buy their hardware, and by preventing other browser engines from running on iOS. Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix before push comes to shove. Microsoft unfortunately did not seem to be able to financ…

When MS prevented other browsers from working well in Windows it was slapped with antitrust. Why is it ok when Apple does it? Is it because macos and ios don't have the same level of os monopoly that MS had back then?

Re: WebKit Tracking Prevention Policy

#208
post #179

Earlier quoted context omitted.

Yes, competing with Google is still a main challenge. Still, Apple seems to be managing by providing the browser for free as a value-add when you buy their hardware, and by preventing other browser engines from running on iOS. Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix before push comes to shove. Microsoft unfortunately did not seem to be able to financ…

> Apple seems to be managing by providing the browser for free Plus @icloud.com email service > Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix I honestly do not see how. Sticking to Safari for now.

Mozilla is looking into becoming more independent from Google by introducing paid services, such as ad-free content subscriptions using Scroll, Pocket, VPN...

Their approach relies on acquisitions (Pocket) or partnerships/experiments (Scroll).

The language used by them when referring to Google has changed quite a lot in the past year or so.

Re: WebKit Tracking Prevention Policy

#209

Earlier quoted context omitted.

> Apple seems to be managing by providing the browser for free Plus @icloud.com email service > Mozilla's financial dependence on Google is still a major challenge, which they'll hopefully be able to fix I honestly do not see how. Sticking to Safari for now.

Mozilla is looking into becoming more independent from Google by introducing paid services, such as ad-free content subscriptions using Scroll, Pocket, VPN... Their approach relies on acquisitions (Pocket) or partnerships/experiments (Scroll). The language used by them when referring to Google has changed quite a lot in the past year or so.

[deleted]

Re: WebKit Tracking Prevention Policy

#210
The fact that this makes behavioural targeting even harder makes me very happy.

What makes me even more happy is that this helps to eliminate the argument stating that 3p cookies can be replaced with heuristics/non-deterministic targeting. So, instead of assigning resources to just another way of targeting users (e.g. hacks, fingerprinting) a developer/PM can already say that these approaches will be prevented in the exact same way. Any further work in this direction would be pointless.

Ideally, we'd put more focus on contextual targeting, which is arguably more useful, significantly less creepy and less dubious from the ethical point of view.

I just wish Microsoft moved in the same direction with IE. So far they've been more quiet on that subject than Google. That's wishful thinking, I know.

Post reply on HN