Mopidy does indeed still use libspotify through our pyspotify Python 3 bindings. Search and everything relating to playlists is broken in libspotify[0] so we us

Mopidy does indeed still use libspotify through our pyspotify Python 3 bindings. Search and everything relating to playlists is broken in libspotify[0] so we use the Web API for this functionality in Mopidy 3 (just released). Spotify's newer browser-only streaming library is useless to us. I believe that librespot (at least one of the implementations) now supports audio from Spotify's new HTTP endpoints, rather than via the 'Mercury' protobuf stuff that libspotify uses. The point being that it might still have a future after Spotify finally kills the remaining parts of libspotify. Disclaimer: I'm a Mopidy developer. [0] https://jodal.no/2016/02/18/guide-to-poor-api-management/ https://jodal.no/2016/02/18/guide-to-poor-api-management/ Edit: oh, and you do need an API key to use libspotify, which Spotify no longer provide. So that kills off any new users from adopting libspotify/pyspotify, even if they could live with the short-commings.