- From: Tim Panton via GitHub <sysbot+gh@w3.org>
- Date: Sat, 25 Jun 2022 13:34:10 +0000
- To: public-webrtc-logs@w3.org
Sure, but I'm afraid my scenario is plausible and yours hopefully isn't because it involves a _lot_ of compute cycles to add and detect watermarks and they offer no user benefit. CropTarget UUIDs are lightweight and offer apparent user benefits. My point is that you can get all the user benefit without the risks by keeping it as an opaque token. My example wouldn't be described as tracking, it would be 'enhanced collaboration', but of course once the data arrived it would be irresistible to use it in _additional_ ways. -- GitHub Notification of comment by steely-glint Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1166287973 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 25 June 2022 13:34:12 UTC