Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
My raspotify/librespot install stopped working last week until i blocked apresolve.spotify.com on my network.
It seems they are switching some regions to a CDN that is not supported by librespot. There is some discussion on the librespot issues github page (https://github.com/librespot-org/librespot/issues/972)
It's really sad as this library has no official replacement. There's libraries like the Web API, but this is a library running on a browser. libspotify allowed playback for custom applications (such as Mopidy[1]).
Yeah it sucks, I found mopidy-spotify to be janky in it's usage but it was the least worst means of playing audio from various backends. It doesn't look like there's much hope for it in the future https://github.com/mopidy/mopidy-spotify
Plugging my ex-colleague's Spotify client called Psst[0] and built with Rust. Not as feature-full than the official client (yet) but way lighter and gets the job done.
Nice, bookmarked it.
For anyone on GNOME I'd recommend Spot
This is only peripherally related, but if you were using libspotify to work on a a command line client, I have an alternative approach. Shpotify offers command line control of the Spotify app on Macs: https://github.com/hnarayanan/shpotify
Cool to see someone who worked on this :) Back in the day I wrote a (probably really bad, not a C/C++ developer) wrapper around libspotify for Node.js: https://github.com/FrontierPsychiatrist/node-spotify
At some point it could do enough for me to build a webapp with Node.js running on a Rapsberry Pi to stream Spotify.
I even got contacted by Spotify to take down the domain node-spotify.com for it.
The way auth tokens are setup for Mopidy-Spotify *you* hold the encryption key for the blob with the OAuth data, and the intermediate server just has an id and the encrypted data. Note that the id is not a Spotify OAuth client-id but an internal one. This is done so we don't have to ship Mopidy-Spotify with the client-secret for the App registration (this was pre PKCE auth).
I.e. I would be highly surprised if our OAuth integration was the source for this issue, but I'm obviously biased as the author of https://github.com/adamcik/oauthclientbridge
As for libspotify, there you had to put in a (device) password and username, so if something scraped that config I guess all bets are off...
Related posts
- Spotify CEO Daniel Ek tells investors Apple's DMA rules are a 'farce'
- 2023 Dec 4 Stickied -FAQ- & -HELPDESK- thread - Boot problems? Power supply problems? Display problems? Networking problems? Need ideas? Get help with these and other questions!
- Resources for flip phone app development?
- spotifly - Spotify library in typescript without using the Spotify Web API.
- Trying to cross compile spotify for my remote vacuum cleaner