no worries, it's good being aware of possible wrongful edits
2025-04-01 09150, 2025
tagomago joined the channel
2025-04-01 09154, 2025
wileyfoxyx[m] has quit
2025-04-01 09122, 2025
SigHunter has quit
2025-04-01 09141, 2025
___nick___ joined the channel
2025-04-01 09129, 2025
SigHunter joined the channel
2025-04-01 09129, 2025
___nick___ has quit
2025-04-01 09125, 2025
___nick___ joined the channel
2025-04-01 09156, 2025
___nick___ has quit
2025-04-01 09119, 2025
___nick___ joined the channel
2025-04-01 09136, 2025
___nick___ has quit
2025-04-01 09101, 2025
___nick___ joined the channel
2025-04-01 09113, 2025
rustynova[m]
The upcoming feature to add dances to MusicBrainz is pretty neat, ngl
2025-04-01 09155, 2025
___nick___ has quit
2025-04-01 09149, 2025
daleo[m] has quit
2025-04-01 09155, 2025
lazybookwyrm[m] has quit
2025-04-01 09114, 2025
reosarevok[m]
rustynova: not sure if that was a small april joke but thanks for the reminder that "member of" needed a free text attribute that can be used to indicate dancers (and other stuff)
2025-04-01 09140, 2025
reosarevok[m]
I had merged code to make it possible almost a year ago, then I forgot to add it until now 😅
2025-04-01 09151, 2025
RustyNova[m]1 joined the channel
2025-04-01 09152, 2025
RustyNova[m]1
Aprils successfully fooled~
2025-04-01 09152, 2025
RustyNova[m]1
But I was talking about more of the choreography than the people doing it
2025-04-01 09126, 2025
reosarevok[m]
Well, one step at a time
2025-04-01 09141, 2025
reosarevok[m]
(that's also how you'd store a choreography, coincidentally)
2025-04-01 09147, 2025
vardhan_ joined the channel
2025-04-01 09107, 2025
crism has quit
2025-04-01 09132, 2025
m1gr has quit
2025-04-01 09158, 2025
m1gr joined the channel
2025-04-01 09150, 2025
crism joined the channel
2025-04-01 09147, 2025
cloverfield has quit
2025-04-01 09123, 2025
minimal joined the channel
2025-04-01 09147, 2025
agatzk[m] has quit
2025-04-01 09106, 2025
volumetrique0[m] joined the channel
2025-04-01 09106, 2025
volumetrique0[m]
CRAP has it ever happened that you created a release EXACTLY when someone else did
I've got a bot that scrapes release groups on MusicBrainz to get album release dates, but it doesn't always work right. As far as I can tell, release groups don't really have "release dates", only releases do. So I'm using the heuristic that my bot should use the earliest date of an official release in a release group.... (full message at
mightytyguy (@_discord_694001273074352208:chatbrainz.org) Musicbrainz does not prefill the date, but all components are optional (so e.g. if you just know that an album was release in April 1995, the release date would be `1995-04`). In this case it's quite likely to be a mistake though
2025-04-01 09131, 2025
elomatreb[m]
confirming release dates is hard, especially for pre-digital stuff, but in this case I think I would consider it justified to fix the date by removing the -01 part
2025-04-01 09101, 2025
elomatreb[m]
otherwise your heuristic for generating the earliest release date of an "album" in the abstract sense is generally what you want
2025-04-01 09100, 2025
aerozol[m] joined the channel
2025-04-01 09101, 2025
aerozol[m]
mightytyguy: Do you need a bot or could you be using the data dumps? I’ll let the devs pipe in if needed, because I don’t really know the technicalities, but we have been facing some trouble with AI scrapers recently. IPs are being blocked left, right and center! Just a heads up that if you are unable to connect to MB one day soon then you should probably have a chat with zas (IP access overlord)
2025-04-01 09141, 2025
rustynova[m]
Wait, I swear I saw a field on the API result for earlies release
2025-04-01 09137, 2025
rustynova[m]
Take `first-release-date`. It should only take official releases
