Description
Recently, MusicBrainz has been unreliable sometimes, as AI scrapers have been overloading the site. This causes listens to be submitted without additional metadata, which is unfortunate.
One fix would be to switch to a self-hosted mirror server. Unfortunately, this has the disadvantage that newly added recordings are only available after the next replication, which only happens once a night. As a workaround, the plugin should try to fetch data from a mirror first and fall back to the official MusicBrainz server in case it cannot find metadata for the current song on the mirror.
Proposed solution
In theory, the current MusicBrainz API client in the plugin could handle this transparently when fetching metadata. The configuration part probably requires the most effort.
Additional context
It would be useful to support some kind of authentication for the mirror server, i.e., basic auth, configured through a .netrc file.
Description
Recently, MusicBrainz has been unreliable sometimes, as AI scrapers have been overloading the site. This causes listens to be submitted without additional metadata, which is unfortunate.
One fix would be to switch to a self-hosted mirror server. Unfortunately, this has the disadvantage that newly added recordings are only available after the next replication, which only happens once a night. As a workaround, the plugin should try to fetch data from a mirror first and fall back to the official MusicBrainz server in case it cannot find metadata for the current song on the mirror.
Proposed solution
In theory, the current MusicBrainz API client in the plugin could handle this transparently when fetching metadata. The configuration part probably requires the most effort.
Additional context
It would be useful to support some kind of authentication for the mirror server, i.e., basic auth, configured through a
.netrcfile.