News for hackers. Stuff that matters.
Re:Web Environment Integrity API by ahahahahah on Friday July 21, 2023 @03:06PM (#36818074)
And thank god for that, otherwise we'd still need to support flash to use most popular websites.
Re:Web Environment Integrity API by tentacleuno on Friday July 21, 2023 @03:07PM (#36818099)
EME is for DRM'ing media. I don't see how that pertains to Flash.

WebAssembly exists as a replacement now, too.

Re:Web Environment Integrity API by wmf on Friday July 21, 2023 @03:12PM (#36818164)
Back in the days before the <video> tag, Web sites were using Flash to play video. Flash was also the main way to play DRMed video before EME.
Re:Web Environment Integrity API by veave on Friday July 21, 2023 @03:11PM (#36818139)
If browsers didn't natively support DRM then they would have to come up with external extensions (such as Flash) to support DRM.

DRM isn't going away.

Re:Web Environment Integrity API by apostacy on Friday July 21, 2023 @04:57PM (#36819618)
DRM should be inconvenient and expensive. There have always been ways to implement DRM security theater for the comfort of content providers in board rooms.

The media ecosystem is not going to be enhanced by making DRM more restrictive. Netflix could completely deactivate all DRM today, and it would change nothing.

Apple completely abandoned their "FairPlay" iTunes music DRM because it became evident that it was not needed.

Re:Web Environment Integrity API by HideousKojima on Friday July 21, 2023 @09:24PM (#36822233)
Every single Netflix show is available on the pirate bay, but Netflix still insists on using DRM.
Re:Web Environment Integrity API by PlutoIsAPlanet on Friday July 21, 2023 @10:48PM (#36822686)
Because Hollywood mandates that legal distribution have DRM.
Re:Web Environment Integrity API by Mindwipe on Saturday July 22, 2023 @03:27AM (#36824164)
Apple in no way abandoned FairPlay. Every file on Apple Music, and iTunes Match is protected with it. And those greatly outnumber transactional sales through the iTunes store, by an order of magnitude. The customer picked the DRMed version, every time.
Re:Web Environment Integrity API by tn5421 on Sunday July 23, 2023 @11:50PM (#36842933)
Because everyone else pirated to great effect.
Re:Web Environment Integrity API by apostacy on Friday July 21, 2023 @04:47PM (#36819488)
Good. DRM should be external to the browser, not integrated into it.

DRM is mostly security theater anyway. Until a few years ago, the Spotify client just left unencrypted mp3s cached locally. And they stopped DRMing music over a decade ago. People are willing to pay a reasonable price for first party content.

If a company insist on DRM, then they should be on their own.

If we make it too easy, then they will just use it everywhere.

Re:Web Environment Integrity API by flangola7 on Friday July 21, 2023 @04:54PM (#36819590)
Spotify will not load in a browser without a DRM plugin
Re:Web Environment Integrity API by apostacy on Friday July 21, 2023 @04:58PM (#36819642)
Yes, but that is fairly recent! Did anyone even notice? For years, you could siphon every song you listened to and save it locally. But did it affect anything? I did it for a little while, but then found it wasn't worth the trouble.
Re:Web Environment Integrity API by Mindwipe on Saturday July 22, 2023 @03:29AM (#36824175)
It affected Spotify enough to engineer a solution to stop it.

And five years isn't "fairly recent".

One would also note Spotify is a failing business, and it was failing even harder then.

Re:Web Environment Integrity API by apostacy on Sunday July 30, 2023 @10:13PM (#36938114)
The majority of Spotify's lifetime there was NO DRM, and ripping it was easy.

The majority of users had no idea and it didn't affect them at all. Nor is there any evidence that it had any impact on Spotify's business.

Re:Web Environment Integrity API by flangola7 on Monday July 24, 2023 @11:37PM (#36857562)
Recent? I signed up 4 years ago and this has always been the case.