Links to external repos?

[AramZS]

Do we want a section of this repo to contain links to other repositories that contain the proposals we are currently considering or previously discussed?

[wseltzer]

Good idea! I'm aware of

• https://github.com/siyengar/private-fraud-prevention
• https://github.com/csharrison/conversion-measurement-api
• https://trac.webkit.org/wiki/ad-click-attribution-draft-spec -> https://github.com/WICG/ad-click-attribution

[wseltzer]

• https://github.com/dvorak42/trust-token-api

[AramZS]

Thanks! I think also good to add https://webkit.org/tracking-prevention-policy/ as something we are looking at.

[AramZS]

And another - https://github.com/bslassey/privacy-budget

[AramZS]

Adding another - https://github.com/mikewest/first-party-sets

[AramZS]

Another sub topic we are discussing under one of the previous setups - https://github.com/csharrison/conversion-measurement-api/blob/master/AGGREGATE.md

[AramZS]

Mentioned - https://w3c.github.io/privacy-considerations/

[wseltzer]

Oct 3, https://github.com/csharrison/aggregate-reporting-api

[ssanjay-saran]

https://github.com/w3c/web-advertising/blob/master/private-lift-measurement-conceptual-overview.md

[AramZS]

Nov 21: https://github.com/bslassey/ip-blindness/

[michaelkleber]

Jan 16, 2020: TURTLEDOVE
https://github.com/michaelkleber/turtledove

[azaroth42]

This is not exactly a web advertising or business use case, but we believe that it is directly relevant and demonstrates a useful application of the same approaches without any commercial interests. Nor is it a direct proposal, but an example of the hoops that we are currently jumping through for a very similar scenario. A scenario that could potentially be made much easier, or completely impossible depending on your deliberations.

The IIIF community has specified, built and adopted several interlinking APIs for engaging with digitized and digital cultural heritage. It is now used by thousands of organizations to provide an improved user experience when interacting with high resolution images. Some of the images are not available without authentication for various reasons but we do not propose to create new authentication patterns, instead to facilitate the user to obtain the regular authentication tokens (typically a cookie) without leaving an in-page client application. As a single session might involve authenticating to many different sites, third party cookies are a very important technology, and we would greatly prefer to use a standard technology than our current arms-race style workaround.

We would be very happy to participate and provide further use case clarification if that would be possible.

[tomcrane]

Hi, where would be the best place to engage with the W3C on the issue raised by @azaroth42 above?

#22 (comment)

We would really like to find a solution for these use cases, which are all about collaboration and interoperability for digitised cultural heritage.