It seems like they want to add MusicBrainz data as they made a PR to my rust API bindings. Not sure if it needs to be checked out
2025-07-02 18333, 2025
petitminion has quit
2025-07-02 18317, 2025
anonn joined the channel
2025-07-02 18300, 2025
Island has quit
2025-07-02 18311, 2025
yvanzo[m] joined the channel
2025-07-02 18312, 2025
yvanzo[m]
<thermospore[m]> "musicbrainz down everyone panic..." <- Sorry about that, it was due to maintenance operations and unexpected.
2025-07-02 18311, 2025
thermospore[m]
All good :)
2025-07-02 18320, 2025
reosarevok[m]
mayhem: ^ in case it's important at some point, see rustynova's post from earlier :)
2025-07-02 18326, 2025
rustynova[m]
I'm not quite sure how it works nor how to contribute because it's all hidden behind buzzwords and stuff so...
2025-07-02 18327, 2025
rustynova[m]
It seems both pay-to-add and get paid for adding? Very confusing stuff
2025-07-02 18351, 2025
mayhem[m] joined the channel
2025-07-02 18351, 2025
mayhem[m]
<reosarevok[m]> "mayhem: ^ in case it's important..." <- yeah, this dude thinks he's building all the solutions for the music industry by handing them a blockchain. kept trying to work with us, but refusing any sort of feedback about how futuile that project is. set phasors to ignore.
2025-07-02 18309, 2025
reosarevok[m]
Ah, ok, so you are aware. I meant more in case they ever make any money
2025-07-02 18355, 2025
mayhem[m]
reosarevok[m]: if they do, I'll go collect some money. but I am not holding my breath, pickle or blockchain.
2025-07-02 18335, 2025
rustynova[m]
Definitely an over-engineered thing. However I'll gladly accept the contributions~
2025-07-02 18333, 2025
UltraFuzzy has quit
2025-07-02 18337, 2025
zoedivision[m] joined the channel
2025-07-02 18338, 2025
zoedivision[m]
honestly when bands first started doing NFT-related releases, before I had any real grasp of what it was supposed to be (honestly I still don't), I thought it seemed like a decent idea — in my mind it seemed like a way to provide a more concrete form of ownership of digital copies...... not the nonsense it all ended up being
2025-07-02 18315, 2025
zoedivision[m]
I've got my hands on this older CD (Prefab's "Jordan: The Comeback") whose disc ID is unique and doesn't exist in the database yet;
2025-07-02 18315, 2025
zoedivision[m]
but the edition it seems to match (straightforward OG US release) *is* there, with two disc IDs already attached;
2025-07-02 18315, 2025
zoedivision[m]
so I have to presume this is just a minor re-press of the same edition...... and if it's worth adding in another release where pretty much all the info will look identical save for the disc ID
2025-07-02 18319, 2025
zoedivision[m]
meant to say, "...and I'm wondering if it's worth adding..."
2025-07-02 18327, 2025
elomatreb[m] joined the channel
2025-07-02 18328, 2025
elomatreb[m]
If there is no other difference and the track times aren’t hugely different you can add the disc ID to the existing release
2025-07-02 18316, 2025
zoedivision[m]
that's the more elegant solution I preferred 😃
2025-07-02 18342, 2025
dylanj joined the channel
2025-07-02 18301, 2025
zoedivision[m]
I get anxious sometimes about all the older submissions in the DB that must have disc IDs attached that should have gone into other editions like box sets or anniversary editions or what-have-you 🙈
2025-07-02 18346, 2025
elomatreb[m]
Historically MB didn’t have releases and release groups and attached all variations to a single release with multiple release events and labels
2025-07-02 18337, 2025
Cheezmo_
There are tons of wrong discids out there. The problem is while it is easy to verify that a disc in hand belongs to a certain release, it is near impossible to know if there is a bad discid that should be removed. There are some obvious cases with very unique pressings but that is not very common.
2025-07-02 18321, 2025
Lotheric[m]
https://accuraterip.com/ has a database of CDs extracted with Exact Audio Copy. It would be nice if we could make use of it here at MB
2025-07-02 18305, 2025
UltraFuzzy joined the channel
2025-07-02 18312, 2025
xarph_ joined the channel
2025-07-02 18327, 2025
xarph has quit
2025-07-02 18331, 2025
Maxr1998 joined the channel
2025-07-02 18303, 2025
Maxr1998_ has quit
2025-07-02 18328, 2025
crazyroostereye joined the channel
2025-07-02 18306, 2025
AJ_Z0 has quit
2025-07-02 18340, 2025
AJ_Z0 joined the channel
2025-07-02 18340, 2025
AJ_Z0 has quit
2025-07-02 18340, 2025
AJ_Z0 joined the channel
2025-07-02 18353, 2025
Erin has quit
2025-07-02 18301, 2025
Erin joined the channel
2025-07-02 18310, 2025
phunyguy has quit
2025-07-02 18312, 2025
phunyguy joined the channel
2025-07-02 18300, 2025
kour1er has quit
2025-07-02 18318, 2025
kour1er joined the channel
2025-07-02 18309, 2025
gianlucas94[m] has quit
2025-07-02 18307, 2025
msmorale[m] has quit
2025-07-02 18315, 2025
Sharpie has quit
2025-07-02 18310, 2025
Sharpie joined the channel
2025-07-02 18303, 2025
xarph_ has quit
2025-07-02 18325, 2025
xarph joined the channel
2025-07-02 18329, 2025
leftmostcat[m] joined the channel
2025-07-02 18329, 2025
leftmostcat[m]
Anyone have info on JonnyJD's isrcsubmit dev branch?
2025-07-02 18329, 2025
leftmostcat[m]
Wondering what it changes (and whether it has OAuth support).
2025-07-02 18348, 2025
crazyroostereye has quit
2025-07-02 18302, 2025
Cheezmo_ has quit
2025-07-02 18334, 2025
Cheezmo_ joined the channel
2025-07-02 18347, 2025
HSOWA has quit
2025-07-02 18306, 2025
HSOWA joined the channel
2025-07-02 18306, 2025
HSOWA has quit
2025-07-02 18306, 2025
HSOWA joined the channel
2025-07-02 18329, 2025
Cheezmo_ has quit
2025-07-02 18343, 2025
Cheezmo_ joined the channel
2025-07-02 18346, 2025
ozonezhou joined the channel
2025-07-02 18347, 2025
AJ_Z0 has quit
2025-07-02 18340, 2025
AJC_Z0 joined the channel
2025-07-02 18307, 2025
AJC_Z0 is now known as AJ_Z0
2025-07-02 18300, 2025
anonn has quit
2025-07-02 18317, 2025
ozonezhou has quit
2025-07-02 18348, 2025
aerozol[m]1 joined the channel
2025-07-02 18349, 2025
aerozol[m]1
zoe.division: imo, if you look at the edit history and the other DiscID’s were added way back when (in the change to NGS every discID in a group was duplicated to every release), and are attached to multiple releases, add yours and wipe the others. It’s impossible to prove a negative, so it’s the only way to eventually get everything correct
2025-07-02 18332, 2025
aerozol[m]1
(doubling up on what others have said, but adding more explicit ‘permission’ to delete em!)
