Last.fm's API will soon be accessible only to subscribers This was largely expected. #lastfm has struggled to find revenue sources for a long time. After losing its radio and streaming capabilities , it simply became a website that collected your music stats. It may offer some fancier reports to paid users, but these are barely the kind of killer features that convince people to part with their hard-earned cash, especially when other streaming apps gradually filled most of the gaps that required a 3rd-party service like last.fm to exist. The obvious solution was to make the last valuable asset they have (API access) also paid. This is a problem if you are using a custom app for scrobbling, like mopidy-scrobbler (or, of course, my Platypush last.fm plugin ), or you just want a way to programmatically fetch your stats. It also means that, unless you pay for a subscription, you will only be able to scrobble your listening stats from an app that already has a pre-existing last.fm API key (e.g. Spotify or Tidal). This is particularly ironic because just in May last.fm broke out of Paramount Skydance and became an independent company again, and it promised that your scrobbles were safe - sure, unless you try and retrieve them over API or build your own scrobbling app, in that case you now need a subscription. The main FOSS alternative to last.fm, Libre.fm, is completely rotten. It has been hovering in a state of uncertainty for too long, it closed sign ups for months, it's behind Cloudflare, it aggressively throttles VPN clients and private browsers, and it's not even open anymore - its Github repo is gone . This is a big motivation for me to invest more efforts into improving the listening stats in Songhive , and perhaps extract the stats ingestion and aggregation component into a stand-alone piece of software that can also be used or integrated in other projects. This is already something that has been running on top of my mind for a while - my article on how to automate music stats , as well as generating things like Discovery Weekly or Release Radar playlists, dates back to 2022. But it still relied on last.fm's API to scrape listening stats coming from other streaming apps, as well as to find similar tracks and artists to those in one's own collection. I feel like we as a FOSS community should be able to walk on our own legs, as both last.fm and libre.fm are no longer reliable solutions. And this is also the right chance to think of a proper #ActivityPub implementation of "Listening" activities in order to replace also last.fm's social features - this is an idea that has been hovering around for a while , but I think it never went beyond the brainstorming phase. The main blocker however will still be the long tail of music apps out there that currently only support last.fm scrobbling. I wouldn't mind building a last.fm clone that also exposes the same API. But last.fm has been around for more than 20 years, and most of the apps have simply hardcoded their API domain into their code - AFAIK nobody thought of supporting custom scrobbling URLs.
Last.fm's API will soon be accessible only to subscribers
This was largely expected. #lastfm has struggled to find revenue sources for a long time.
After losing its radio and streaming capabilities, it simply became a website that collected your music stats.
It may offer some fancier reports to paid users, but these are barely the kind of killer features that convince people to part with their hard-earned cash, especially when other streaming apps gradually filled most of the gaps that required a 3rd-party service like last.fm to exist.
The obvious solution was to make the last valuable asset they have (API access) also paid.
This is a problem if you are using a custom app for scrobbling, like mopidy-scrobbler (or, of course, my Platypush last.fm plugin), or you just want a way to programmatically fetch your stats.
It also means that, unless you pay for a subscription, you will only be able to scrobble your listening stats from an app that already has a pre-existing last.fm API key (e.g. Spotify or Tidal).
This is particularly ironic because just in May last.fm broke out of Paramount Skydance and became an independent company again, and it promised that your scrobbles were safe - sure, unless you try and retrieve them over API or build your own scrobbling app, in that case you now need a subscription.
The main FOSS alternative to last.fm, Libre.fm, is completely rotten. It has been hovering in a state of uncertainty for too long, it closed sign ups for months, it's behind Cloudflare, it aggressively throttles VPN clients and private browsers, and it's not even open anymore - its Github repo is gone.
This is a big motivation for me to invest more efforts into improving the listening stats in Songhive, and perhaps extract the stats ingestion and aggregation component into a stand-alone piece of software that can also be used or integrated in other projects.
This is already something that has been running on top of my mind for a while - my article on how to automate music stats, as well as generating things like Discovery Weekly or Release Radar playlists, dates back to 2022. But it still relied on last.fm's API to scrape listening stats coming from other streaming apps, as well as to find similar tracks and artists to those in one's own collection.
I feel like we as a FOSS community should be able to walk on our own legs, as both last.fm and libre.fm are no longer reliable solutions.
And this is also the right chance to think of a proper #ActivityPub implementation of "Listening" activities in order to replace also last.fm's social features - this is an idea that has been hovering around for a while, but I think it never went beyond the brainstorming phase.
The main blocker however will still be the long tail of music apps out there that currently only support last.fm scrobbling.
I wouldn't mind building a last.fm clone that also exposes the same API. But last.fm has been around for more than 20 years, and most of the apps have simply hardcoded their API domain into their code - AFAIK nobody thought of supporting custom scrobbling URLs.