MusicBrainz Server update, 2025-12-16

We are back with one last small release before the holidays, which mostly improves URL handling, fixing some broken cleanups and allowing linking to a few new databases. We are also including one small new feature, allowing to browse events by series in the API (to get, for example, all the concerts in a tour in one go). And finally, recording and release group edits entered while editing a release will now also indicate the release they were entered from, mirroring the feature that we recently added for the relationship editor.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to Jim DeLaHunt and owlpharoah for having contributed to the code. Thanks to Anesidora, Aszazin, dvirtz, fabi123, finalsummer, Griomo, Raman Sinclair, Relaxo5, sanojjonas, yindesu and xodus for having reported bugs and suggested improvements. Thanks to Avava_Ava, Besnik, Echelon, GABG, LeoVallejo, Pioneers, kKZvtcqX, karpuzikov, mfmeulenbelt, miausalvaje, salo.rock, wileyfoxyx and yyb987 for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2025-12-16.0.

Continue reading “MusicBrainz Server update, 2025-12-16”

We can’t have nice things… because of AI scrapers

In the past few months the MetaBrainz team has been fighting a battle against unscrupulous AI companies ignoring common courtesies (such as robots.txt) and scraping the Internet in order to build up their AI models. Rather than downloading our dataset in one complete download, they insist on loading all of MusicBrainz one page at a time. This of course would take hundreds of years to complete and is utterly pointless. In doing so, they are overloading our servers and preventing legitimate users from accessing our site.

Now the AI scrapers have found ListenBrainz and are hitting a number of our API endpoints for their nefarious data gathering purposes. In order to protect our services from becoming overloaded, we’ve made the following changes:

  • The /metadata/lookup API endpoints (GET and POST versions) now require the caller to send an Authorization token in order for this endpoint to work.
  • The ListenBrainz Labs API endpoints for mbid-mapping, mbid-mapping-release and mbid-mapping-explain have been removed. Those were always intended for debugging purposes and will also soon be replaced with a new endpoints for our upcoming improved mapper.
  • LB Radio will now require users to be logged in to use it (and API endpoint users will need to send the Authorization header). The error message for logged in users is a bit clunky at the moment; we’ll fix this once we’ve finished the work for this year’s Year in Music.

Sorry for these hassles and no-notice changes, but they were required in order to keep our services functioning at an acceptable level.