Last.fm will start charging for API keys since December 1st

Sounds like bad news. Unless ListenBrainz gets an exception (and why would Last.fm grant one?), Last.fm importer will stop working for good.

6 Likes

Maybe MeB should post this on socials and say somthing like “Use your last chance to freely migrate to ListenBrainz”

3 Likes

This is bad news for Navidrome too, since scrobbling uses your own API key. Also pretty annoying for them to announce it 2 weeks before it takes effect, doesn’t give much time to prepare for it.

To me it sounds like it’s the end of Last.fm scrobbling from FOSS applications in general. Hard to imagine that a hobbyist developer who contributes a Last.fm plugin for their music player will pay $5/month just to keep it working. Unless they will require their users to provide their own API keys, like Navidrome.

Perhaps it’s time to prepare for another wave of increased ListenBrainz traffic, like a few months ago when Last.fm introduced scrobbling limits?

4 Likes

Poor ListenBrainz can’t catch a break

Back then: Paying to edit scrobbles.
Now: Paying to keep your API key.

:clown_face:

Satirical parody of their announcement. Who dares to post it in their forum? :rofl:

From the 1st of December (and every day since September 17, 2015), holding a ListenBrainz user token will require a free ListenBrainz account. Getting a token happens automatically when you sign up (clicking “Reset token” rotates it), and existing tokens will continue working indefinitely without a credit card.

This applies to everyone. Whether you’re using an app someone else built, self-hosting your own music server, or writing a terrible Python script at 2 AM, you don’t need a Pro account, and your listens will keep working because we didn’t put a toll booth on basic functionality.

Why we’re doing this

We have always supported the developer community, and we are deeply grateful for all of the interesting, useful, and brilliant projects developers have built over the years—especially the ones that let you submit listens from devices and players beyond our official Android app and Spotify sync, because we rely on an open API instead of corporate gatekeeping. We think you’re awesome.

Unlike proprietary platforms, our public API has straightforward rate limits (one request per second) and infrastructure built for the community—and if you actually want bulk access, our public listen data is CC0 public domain and we literally publish full compressed JSON and PostgreSQL dumps (plus Spark-ready monthly archives) twice a month so nobody has to scrape the API in the first place. Linking API access to a free account helps ensure that API users are both part of the open-source community and not getting extorted for $50 a year.

This will be a new cost to none of you, and we understand that it means indie developers won’t have to discontinue their passion projects. We can assure you that we took this decision very lightly.

Who this change affects:

  • Affected: Anyone who likes owning their own listening history.
  • Not affected: Venture capitalists, corporate partners, and people who enjoy begging partners@ for permission to run a hobby project.

We aren’t reaching out to “a handful of free tools” to offer them a special whitelist, because every free tool is already allowed to exist.

What donating to MetaBrainz gets you

Donating to the non-profit MetaBrainz Foundation helps support ListenBrainz and the future development of open music data. In addition to warm fuzzy feelings and some optional cosmetic username flair, donating unlocks zero functional paywalls, because we don’t lock basic things like editing metadata (over on MusicBrainz), viewing historical Year in Music reports, or browsing without ads behind a subscription.

What to do next

  • If you own a token and you’re building a non-commercial project for yourself or other users, please keep doing what you’re doing.
  • If you’re building something commercial, or using the data for research, a gentle reminder that our public listen dumps are CC0 public domain. You don’t need to email partners@ and wait 10 business days for permission—just respect the API rate limits, consider signing up as a MetaBrainz commercial supporter if you’re building a business on it at scale, and don’t be evil.

Made with AI

3 Likes

“writing a terrible Python script at 2 AM”

:+1:

there will be exceptions for some apps they say, but I don’t know how they can reasonably maintain a list of whitelisted apps.

They just shot both of their feet off with a double-barreled shotgun with this one.

2 Likes

Just came here because of this… Looks like my last.fm data isn’t importing though… I wonder if that’s due to all the issues last.fm servers are having today? Or am I doin it wrong?

I wonder why people keep clinging to Last.fm. What more needs to happen to embrace ListenBrainz? Instead of spending money on essential features, donate to LB and enjoy a superior design.

The data is open and accessible; the infrastructure will catch up eventually, and features can be tacked on.

AI tools make it possible for everyone and their dog to whip up a script that transforms raw data into shiny, pretty graphs or stats, if need be.

5 Likes

LB is really good and superior to Last.fm in many respects in my opinion. But whenever I recommend it to Last.fm users, they say its main drawback is the recommendations. It’s a bit of a vicious circle. People are reluctant to take the plunge because they feel the recommendations aren’t as good, but if they don’t get involved, things aren’t likely to improve in that respect.

It would be a good start if this unfortunate change meant that Last.fm users could start scrobbling to LB as well as their usual service.

I wonder why people keep clinging to Last.fm. What more needs to happen to embrace ListenBrainz? Instead of spending money on essential features, donate to LB and enjoy a superior design.

For me the only reason is that iBroadcast.com does not support scrobbling to ListenBrainz.

I do prefer ListenBrainz, but the stats still aren’t quite as powerful, and for some reason it’s still not possible (at least on the frontend) to see how many times I’ve played a song. Unless I’m viewing the all-time stats. Also there’s no viable mobile frontend, and the main app I use for viewing my listens on mobile (Finale) doesn’t support ListenBrainz.

I do think ListenBrainz has the potential to have much better stats, since it’s based on a database compared to Last.fm still not being able to parse featured/multiple artists.

2 Likes

Couldn’t people just change their host files to point to LB?

Not sure what you mean here, there is a first party LB app ?

Finale is specifically a last.fm companion app from my reading, so I don’t see it supporting LB any time soon…

It’s not on iOS right now, which is what I use.

3 Likes

No need for Last.fm to get scrobbling working towards listenbrainz. I have Last.fm scrobbling working on my Hifi App interactive screen (using raspberry pi) and I updated the scrobbling python code with direct Listenbrainz API access, and it works perfect. So, if Last.fm stops on 1 December with free API access, you can continue scrobbling with listenbrainz. All coded in 5min with Gemini Argon :slight_smile:

I have the same issue. Instead I used the 3rd party tool at https://lastfm.ghan.nl/export/ to download the csv/json (no login required), and had AI rewrite it to be compatible as a Listenbrainz import-file.
Select Listenbrainz as service on the import page https://listenbrainz.org/settings/import/ and select the zip-file created by your AI agent.
All my 40998 scrobbles were imported succesfully. :slight_smile: