Devlog 0

I’m creating a MusicBrainz seeder browser extension with automated field matching (using user-defined query scripts), tools for data patching and correcting, and multi-browser support.

It’s gonna primarily be used to get data from digital media releases from music streaming websites, but it could definitely be used to get data from any site with predictable locations of data

ehhhh????

Musicbrainz is (in their own words) “The ultimate source of music information”
imagine Wikipedia, but for music
A MusicBrainz Seeder is a tool used by MusicBrainz editors to auto-fill data fields when submitting entities to the database - kinda like macros
Automated field matching - data can be routed from DOM elements in the active tab to certain data fields about the entity
Tools for data patching and correcting - sometimes when combining data from multiple sources there are slight differences in the wording of fields e.g. “… of …” vs “… Of …”. These conflicts will be presented and the editor will be given the option to choose the best option or use their own.

Story time

This project was initially inspired by Harmony and was going to be almost a complete clone of it, but after spending almost a week coding with this approach, I had to scrap all of it and start from scratch . Due to the CORS restrictions used by the APIs endpoints of the streaming sites, HTTP requests couldn’t be honoured if they came straight from my website; they would instead have to be proxied through a backend server . I had no intention of maintaining any sort of backend, especially for my first project.

Now that I’m going down the browser extension route, I think it’s turned out for the better, especially with query scripts that can be added by the user (I’m still figuring out the complete syntax for them). See the screenshot for an example. I want the design to be understood easily by most MB editors

Technical stack

• wxt - browser extension framework
• svelte - UI library - used in the popup and summary pages