zlacker

[parent] [thread] 4 comments
1. coffee+(OP)[view] [source] 2021-03-05 01:20:33
Won't work.

The proposed designs never expose segments (err, cohorts, whatever) to the page. This machine works for managing targeted advertising in Chrome, and... that's it.

replies(2): >>jrochk+N >>kall+yh
2. jrochk+N[view] [source] 2021-03-05 01:25:55
>>coffee+(OP)
The OP says:

> The draft specification states that a user’s cohort ID will be available via Javascript, but it’s unclear whether there will be any restrictions on who can access it, or whether the ID will be shared in any other ways.

Is this incorrect?

3. kall+yh[view] [source] 2021-03-05 03:29:01
>>coffee+(OP)
No, they explicitly do.

> cohort = await document.interestCohort()

I mean it‘s a proposal. I‘ll believe it when I can use it, but maybe actually look at the proposal.

replies(1): >>coffee+3n
◧◩
4. coffee+3n[view] [source] [discussion] 2021-03-05 04:10:00
>>kall+yh
Oh yeah, sorry, I should have clarified: there are a LOT of followup documents that build on it. The reason I think it won't be an option comes from one of those. (I think FLEDGE, but don't have time to check.)

But like you said, we'll see what they actually ship.

replies(1): >>kall+Xb1
◧◩◪
5. kall+Xb1[view] [source] [discussion] 2021-03-05 11:41:29
>>coffee+3n
Oh that‘s disapointing, if not surprising. Thanks for the clarification. It seems strange that they are willing to give such a boost to small competitors.
[go to top]