Re: [w3ctag/design-reviews] Media Feeds API (#477)

Prompted by seeing the recent intent to ship come through, I want to raise a couple of architectural questions about this proposal.

One of the goals for Media Feeds is to provide personalised media recommendations. To do this, the browser makes an authenticated request to the server, using the website's session cookies. The use of a website's session cookies for what is really a native application feature seems strange to me. Is there precedent in other web platform features here?

Related to this, the spec says there's very low impact on security and privacy, but the proposal exposes personal information to the UA (information about the currently logged in user), makes direct use of session cookies to make authenticated requests, and provides the UA (and its host platform) with media recommendation data which is valuable user insight. Sites would have to limit the scope of any cookie used to fetch the media feed to prevent potential misuse.

Another concern we have with the current design is that there is a limit of one media feed per origin. I raised this [here](https://github.com/WICG/media-feeds/issues/9), but as this is an architectural consideration, I'm interested in the TAG's perspective on this.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/477#issuecomment-652922928