- From: Marvin Brouwer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jan 2025 08:14:41 +0000
- To: public-secondscreen@w3.org
Hmm, I figured it had something to do with security. Didn't think of the fingerprinting. However, from a user standpoint, I'm not particularly happy with the browser scanning my network for cast devices without my consent anyway. So I'd be more than fine with a popup saying something like "chrome would like to scan your network for cast devices". And then make the start of casting similar to playing audio, that it has to be a user interaction. Similar to these things, I'd say iterating Bluetooth and/or usb devices has the same flaws, yet the spec supports this. I'm not a security expert by any means so maybe I'm missing something, but I am experienced with javascript, and from a developer's perspective this is yet another inconsistency in programming api. I'm not sure if this is the right place, but I hope sharing this helps. -- GitHub Notification of comment by Marvin-Brouwer Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/526#issuecomment-2591900780 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 January 2025 08:14:41 UTC