7 ms·
> MediaSession API has been enabled by default which allows web authors to provide custom behaviors for standard media playback interactions, giving them more o
by txutxu 6y ago
> MediaSession API has been enabled by default which allows web authors to provide custom behaviors for standard media playback interactions, giving them more options than ever.
/me checks what is this... then, from the draft (https://w3c.github.io/mediasession/#security-privacy-considerations https://w3c.github.io/mediasession/#security-privacy-conside...):
> The API introduced in this specification has very low impact with regards to security and privacy.
Ok... my concept of privacy, may not be the same as your concept of privacy...
- Spivak 6y agoBut it look like it has zero impact on privacy. Like I don’t get it. This is a website being able to tell the browser, “hey I’m playing $Song” so it can show out-of-page media control buttons like you get on your lock screen. Where’s the issue?
- elcomet 6y agoHow does this have an impact on privacy ? It only allows a website to send you additional information about some media, which you can display or not. It's not sending anything back to the server.
- tephra 6y agoI haven't looked into it much but could it be another point in a browser fingerprint?
- gruez 6y agohow? it looks like all you can do is send some information to the browser, and register some callbacks (if the user presses those keys). I guess you can fingerprint for the existence of the feature, but that's already 100% correlated with the user-agent, so it's a non-issue in my opinion.