undefined | Better HN

0 pointsjmull8y ago0 comments

In this case Apple hasn't implemented a user-hostile feature championed by a rival.

And I guess it's Spotify that made the call to pull the rug out from under their Safari users.

It seems hard to blame Apple here. Should the web standard really just be "whatever Google says?"

That is simpler for web developers, but I think would be terrible for the web as a platform and bad for users.

At some point you have to decide who the web is for, the users or the advertisers and content distributors? Apple is going one way and Google is going another, and I, for one, am happy there isn't universal acceptance of Google's direction, despite the inconvenience to web developers.

0 comments

1 comments · 1 top-level

bzbarsky8y ago

Apple _has_ implemented this user-hostile feature. It's just that they only support Apple's own FairPlay DRM.

So assuming Spotify is contractually required to provide DRM for its music (by the music suppliers), Spotify has the choice of licensing Apple's DRM so it can work with Safari or not working with Safari. Which choice is right depends on the licensing terms, which I have not been able to locate in a quick search.

> Apple is going one way and Google is going another

Not on this topic they're not. Apple has been very firmly in the web media DRM camp all along.

j / k navigate · click thread line to collapse