News for hackers. Stuff that matters.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by davidcbc on Tuesday November 28, 2017 @01:07PM (#15799730)
I doubt that many people are reading ebooks in a context where they need to copy and paste regularly, I could be wrong though. I read exclusively ebooks and it hasn't ever come up that I remember. I'm not saying it isn't a valid use case, but I question whether it is a common use case for the average user.

I'd be curious to know how someone has narrowed down the black box that is Netflix to determine that buffering is caused by the DRM.

Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ... by simion314 on Tuesday November 28, 2017 @04:03PM (#15801590)
Sorry if I was not clear, I suspect that DRM caused the buffering issue, or at least an open source player could be implemented that could keep more back buffer so you can go back 30 seconds. Wouldn't be illegal to reverse engineer the players that include DRM? or you would have to be careful not to look at the bytes that implement the DRM.