It’s possible that if we could patch the system_information_string being used in libspotify’s ClientResponseEncrypted that might be enough. But I’m not sure if that’s possible/realisitic to do… And I don’t time to spend trying right now. Time is probably better spent moving to something based on librespot.
This is so extremely sad!
I spend 100s of hours development time in my project relying on that connection.
Always hoped they never stop supporting it.
It’s so idiotic. What’s there benefit cutting this channel off!?
Presumably their cash flow problems are so bad they’ve had to sell off the machine hosting it. Who knows! Be sure to tell them what you think about this. And tell them what you think about their lack of replacement library, they’ve had 7 years to work on it.
An alternative right now is librespot. And there’s a packaged easy to install version for Raspberry Pi called Raspotify. You can control it headlessly through Spotify Connect (it’s actually the only way to control it). But then you lose support for multiple sources (e.g. local, yotube, soundcloud etc). Might be good enough for some.
Although they made a mess of it (turns out this move also killed their old Apple and Android SDKs, which they forgot to mention) I doubt they’ll do a u-turn. It’s embarrassing enough as it is.
I am testing mopidy-tidal. It is working, except that Tidal’s playlists are not returned from method “core.playlists.as_list” (only local and spotify’s playlists are listed).