News for hackers. Stuff that matters.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by icebraining on Tuesday November 28, 2017 @07:41AM (#15796671)
If it's just to prevent that, you could just have a "copy=false" attribute on the tag, which browsers would respect. No need for proprietary encryption nonsense.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by Mindwipe on Tuesday November 28, 2017 @08:16AM (#15796917)
Browsers didn't respect Do Not Track.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by icebraining on Tuesday November 28, 2017 @08:18AM (#15796927)
I don't understand what you mean. DNT is a flag supposed to be respected by web services, not by browsers.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by logfromblammo on Tuesday November 28, 2017 @09:52AM (#15797712)
Some versions of some browsers turned DNT on by default. Respecting DNT in this instance would have always made this flag a choice by the user.

There is still room to argue that the user's choice was to install a browser that made DNT the default option.

But it's a moot point, since the sort of web services that were in mind when DNT was proposed largely ignored it. They never set the evil bit in their responses, either.