Here's my guess as to what happened.<p>A couple months ago, Spotify switched their web player from using Flash to using HTML5 + DRM (the "standardized" web DRM).<p>At least, that was the case for Chrome and Firefox, which I noticed because I exclusively use the Spotify web player.<p>But I guess Safari doesn't support web DRM via the Widevine CDM. So they must have kept the Flash based web player around for Safari.<p>And, indeed, Flash would only be needed for Safari. Chrome and Firefox support web DRM on Windows, Linux, and AFAIK MacOS too.<p>Now, supporting both a Flash based web player and an HTML5 based web player is a lot of engineering. I'll bet at some point they decided they didn't want to do that. The only reason they still had the Flash player was to support Safari and Safari only has 2% market share. On top of that, I'll bet most of their customers use the desktop app. So of the 2% of Safari users, how many are using the Spotify web player?<p>So they dropped their Flash based player, and thus had to also drop support for Safari.<p>I think it's a fairly reasonable move. Flash is dying; they couldn't keep their player on it, so they _had_ to move to HTML5. Since they have to use DRM at the behest of the RIAA, web DRM thus becomes their only choice.<p>I doubt the story is much better for alternatives. Even if any of the other music subscription platforms are still using Flash, that's unlikely to continue for long.<p>I don't blame Safari for not implementing web DRM. That leaves only one party left to point the finger at; the RIAA. If you need someone to blame, blame them.