3 ms·

> Spotify is in the process of killing the librespot project How could they possibly do that? They cannot prevent people or AI from reverse engineering their A

> Spotify is in the process of killing the librespot project How could they possibly do that? They cannot prevent people or AI from reverse engineering their APIs.

TingPing 1mo ago
Depends on how much they care. They can take down repos containing any keys, or use heuristics to block clients.
hahn-kev 1mo ago
Technically no, but they can just ban you. It would not be impossible to detect.
egeozcan 1mo ago
Anthropic can prevent people from using their models with the subscription plan outside Claude Code, why couldn't Spotify?
- sbinder 1mo ago
  Because millions of Spotify-compatible speakers are sold with firmware that will never be upgraded, so they can't ever change the Spotify connect protocol without breaking those devices.
  - epihelix 1mo ago
    ... and no company ever broke backwards-compatible support.
    - LollipopYakuza 1mo ago
      I'd say it's a good thing they are not (?)
baggachipz 1mo ago
DMCA has entered the chat.
laddershoe 1mo ago
You're right, they can't prevent that, but they can change their APIs in breaking ways enough to make librespot unreliable, to the point it's just not worth it. I assume that for a long time, Spotify was content to ignore projects like librespot... they didn't help those projects, but didn't harm them either, and generally to keep things stable enough that a project based on librespot basically stayed working, which is why you saw so many OSS tools that used it behind the scenes. It does seem like that balance shifted over the last year, and now librespot is constantly breaking in new and mysterious ways. Some accounts work, others don't. Some tracks play, others don't. The devs did a great job fixing that stuff, but it's a game of whack-a-mole, and Spotify seems to have really upped the frequency of how often they break things. And that's for the lossy decoding, which is functionality that used to be pretty stable. Spotify reached out and (I assume) made some threats that explicitly shut down their work around lossless audio [1]. FYI -- I'm not associated with the librespot project, but I was actively working on a project that relied on it. Eventually I gave up in favor of self hosting, because I want my music to not break all the time. Shame, because I used to like Spotify a lot and now I'm actively looking to move away from it. That's one premium family plan subscription they're gonna lose! I'm sure they'll feel the sting. [1] https://github.com/librespot-org/librespot/issues/1583#issuecomment-3499343020 https://github.com/librespot-org/librespot/issues/1583#issue...

> Spotify is in the process of killing the librespot project How could they possibly do that? They cannot prevent people or AI from reverse engineering their APIs.

TingPing 1mo ago

Depends on how much they care. They can take down repos containing any keys, or use heuristics to block clients.

hahn-kev 1mo ago

Technically no, but they can just ban you. It would not be impossible to detect.

egeozcan 1mo ago

Anthropic can prevent people from using their models with the subscription plan outside Claude Code, why couldn't Spotify?

sbinder 1mo ago
Because millions of Spotify-compatible speakers are sold with firmware that will never be upgraded, so they can't ever change the Spotify connect protocol without breaking those devices.
- epihelix 1mo ago
  ... and no company ever broke backwards-compatible support.
  - LollipopYakuza 1mo ago
    I'd say it's a good thing they are not (?)

baggachipz 1mo ago

DMCA has entered the chat.

laddershoe 1mo ago

You're right, they can't prevent that, but they can change their APIs in breaking ways enough to make librespot unreliable, to the point it's just not worth it. I assume that for a long time, Spotify was content to ignore projects like librespot... they didn't help those projects, but didn't harm them either, and generally to keep things stable enough that a project based on librespot basically stayed working, which is why you saw so many OSS tools that used it behind the scenes. It does seem like that balance shifted over the last year, and now librespot is constantly breaking in new and mysterious ways. Some accounts work, others don't. Some tracks play, others don't. The devs did a great job fixing that stuff, but it's a game of whack-a-mole, and Spotify seems to have really upped the frequency of how often they break things. And that's for the lossy decoding, which is functionality that used to be pretty stable. Spotify reached out and (I assume) made some threats that explicitly shut down their work around lossless audio [1]. FYI -- I'm not associated with the librespot project, but I was actively working on a project that relied on it. Eventually I gave up in favor of self hosting, because I want my music to not break all the time. Shame, because I used to like Spotify a lot and now I'm actively looking to move away from it. That's one premium family plan subscription they're gonna lose! I'm sure they'll feel the sting. [1] https://github.com/librespot-org/librespot/issues/1583#issuecomment-3499343020 https://github.com/librespot-org/librespot/issues/1583#issue...