[kitsunesoba]

Considering how long Spotify has been dragging their feet on replacing the long-deprecated libspotify, I can’t agree that they’re the more open of the two options. I’ve been waiting to release a client project built on a messy hybrid of the Spotify REST API (for most functions) and libspotify (for playback) for years now and there’s still no hint of the replacement they’ve been promising.

[jdillaaa]

Last I used libspotify on Linux it still worked, but yes, official support has been withdrawn. It was a hassle to get it working, so yeah it was far from perfect. I found no solutions at all for doing the same with Apple Music though. That has changed a bit recently it seems.

I have a few projects too that involve the hybrid of the REST API and the libraries, it is definitely not ideal (should all be through REST API IMO). I guess Spotify could do it all over the REST API (including playback, Spotify connect, etc.), and then the client would only need to pull in a library that handles content decryption because the API can't send back decrypted audio streams (copyright/pirating). DRM is likely the biggest reason why they haven't done this yet (thoughts?), but the previous solution sounds plausible.

https://github.com/librespot-org/librespot has been a very good replacement for libspotify, and is pretty actively developed. Spotify can of course break this at any minute but it seems unlikely that this would happen.