News for hackers. Stuff that matters.

A comment on New York Times phasing out all 3rd-party advertising data. Parent comment

Re:New York Times phasing out all 3rd-party advertising data by saagarjha on Wednesday May 20, 2020 @02:05PM (#23249893)
I mean, the Safari application is already doing XPC with the web content process constantly anyways. And perhaps they can batch these messages?
[ Parent | on HN ]
Re:New York Times phasing out all 3rd-party advertising data by scarface74 on Wednesday May 20, 2020 @03:10PM (#23250564)
Why would Safari be doing any communication with the content blockers? The content blockers are submitting JSON one time to iOS Safari and aren’t running at all.
[ Parent | on HN ]
Re:New York Times phasing out all 3rd-party advertising data by saagarjha on Wednesday May 20, 2020 @03:16PM (#23250621)
The Safari App Extension is running in the background, which is presumably what the process is communicating with.
[ Parent | on HN ]
Re:New York Times phasing out all 3rd-party advertising data by scarface74 on Wednesday May 20, 2020 @04:48PM (#23251603)
You’re talking about MacOS and not iOS? As far I know, the only time Safari or any other app on iOS calls an extension is when the user chooses to “share” with that extension
[ Parent | on HN ]
Re:New York Times phasing out all 3rd-party advertising data by saagarjha on Wednesday May 20, 2020 @10:13PM (#23254213)
Yeah, I think this API is only available on macOS. On iOS this would require keeping the extension alive in the background, which Apple seems largely opposed to allowing.
[ Parent | on HN ]