I am quite new to both MusicBrainz and ListenBrainz, so please bear with me…
As reported in a different post, I am working on a program that supports tracking Listens on ListenBrainz.
It retrieves its data from certain hardware players, of which none, as far as i know, do provide MusicBrainz ids. I believe that’s the reason why the links on my ListenBrainz user profile page are not clickable.
It would be easy to let the program use MusicBrainz’ REST server to try to locate them, but I assume MusicBrainz server will hate me for all the unneeded traffic (many requests for the same artist/albums over and over again). I want my program to run on Raspberry pi devices, so persisting MusicBrainz ids on the filesystem will not be feasible (it will destroy the pi’s SD card on the long run). Perhaps installing the MB server locally would be a solution, but that seems to be a bit overkill to me.
The solution I’m thinking of is to create a separate web-service for those users that are as obsessed about registering listens as I am and have access to a database server (for example on a (cloud) server), or users that don’t care about damaging their SD cards. It will store the searched artist/albums and the corresponding MusicBrainz ids in a database and provide a simple web UI to manually fix ambiguity (artists that have the same name, etc.).
Any thought on this? Or did I miss a much simpler solution?