I guess it means that Bandcamp ain't the scrappy startup it was way back in 2007.
2023-03-17 07644, 2023
pbryan
I didn't know they were acquired by Epic until I looked them up.
2023-03-17 07612, 2023
mayhem
yep. and they are the shining example of the best the music industry can do. 🤮
2023-03-17 07636, 2023
pbryan
#sad
2023-03-17 07604, 2023
mayhem
#sad but increasingly an #opportunityforchange
2023-03-17 07637, 2023
pbryan
Opportunity for a social enterprise to fill the vacuum?
2023-03-17 07652, 2023
mayhem
communities, not industries. curators, not influencers. creative coops, not licensing collectives
2023-03-17 07641, 2023
pbryan
Sounds good to me.
2023-03-17 07639, 2023
mayhem
I'm ironing out the last kinks to convince myself that a new system is possible. soon I hope to write it up and ask for feedback.
2023-03-17 07606, 2023
mayhem
not sure if Cory should be the first person to comment or people in this channel. tough audiences.
2023-03-17 07658, 2023
Lotheric_ has quit
2023-03-17 07641, 2023
Lotheric joined the channel
2023-03-17 07615, 2023
aerozol
I’ll decide if the Bandcamp union thing reflects badly or well on Bandcamp when we see if Bandcamp lets them unionize… or pulls some shitty moves. I would be really bummed if they do, I don’t know of an alternative to buy the music I want to buy :(
2023-03-17 07627, 2023
pbryan
I guess Magnatune isn't a going concern anymore. Maybe that could get rebooted.
2023-03-17 07616, 2023
jivte joined the channel
2023-03-17 07633, 2023
jivte_ joined the channel
2023-03-17 07612, 2023
jivte has quit
2023-03-17 07614, 2023
jivte_ has quit
2023-03-17 07604, 2023
aerozol
monkey: didn’t get as much done today as I would have liked, but have a look at the LB figma for a new menu + search bar (some other tweaks to the layout to make it fit), plus a mockup for a landing page: https://www.figma.com/file/YRbCOtFHBez8XmMdCKbGta…
2023-03-17 07607, 2023
aerozol
Keen for feedback!
2023-03-17 07614, 2023
lucifer
mayhem: someone reached out to me on email about this project: https://wiki.musicbrainz.org/Development/Summer_o… . i pointed them towards the channel but i see the idea is not in 2023 list. so wanted to confirm whether we want to still do it?
2023-03-17 07603, 2023
lucifer
monkey: will look into it thanks.
2023-03-17 07618, 2023
iconoclasthero has quit
2023-03-17 07644, 2023
iconoclasthero joined the channel
2023-03-17 07613, 2023
zas
aerozol: when people unionize, that's usually under the pressure.
2023-03-17 07600, 2023
aerozol
zas: I haven't looked into it, but in NZ not necessarily I guess. Every big industry should have a union imo. But yeah the vibe on their website is that they've had enough
2023-03-17 07644, 2023
jasje joined the channel
2023-03-17 07632, 2023
d4rk-ph0enix joined the channel
2023-03-17 07630, 2023
d4rkie_ has quit
2023-03-17 07612, 2023
zas
LB team: can you check disk space on gaga? it is reaching red zone, and I think that's related to LB
lucifer: I had removed that from this years list because we didnt want new features such as those right now. but if someone really wants to do it, we'd need to work with them to really defined what this feature is (its not wholly clear to me).
I'm guessing I'm not actually supposed to do [ $voter_args, \@votes, ] when $voter_args is an array ref, since I guess I want that flattened inside the []
2023-03-17 07644, 2023
reosarevok
How did I do that? :D
2023-03-17 07658, 2023
bitmap
right, so I think @$voter_args will fix it
2023-03-17 07603, 2023
bitmap
since those are all scalar args
2023-03-17 07654, 2023
bitmap
[ @$voter_args, \@votes, ] will flatten $voter_args in the containing array
2023-03-17 07618, 2023
atj
isn't that obvious reosarevok?!
2023-03-17 07603, 2023
reosarevok
bitmap: yay. Your search took too long and was cancelled. It may help to be more specific, or to try again.
2023-03-17 07613, 2023
reosarevok
So it won't work but at least it's not crashing, lol
2023-03-17 07637, 2023
reosarevok
(it worked when limiting it to 10 days)
2023-03-17 07654, 2023
reosarevok
I do feel that the way we're looking at beginner here makes stuff super slow though
2023-03-17 07630, 2023
reosarevok
Yeah, if I do "voter is a beginner" and "editor is a beginner" together it times out even for the last 10 days
2023-03-17 07611, 2023
reosarevok
I'm not 100% sure if it's worse than with the previous style, or both just suck equally
2023-03-17 07626, 2023
reosarevok
But I'm starting to feel we need to have triggers to mark if someone is a beginner too tbh
2023-03-17 07657, 2023
bitmap
yea it sounds like something we should materialize somewhere
2023-03-17 07647, 2023
reosarevok
Of course, we just missed the schema change deadline :p
I'm putting it up for now, but we should consider the materializing option
2023-03-17 07610, 2023
reosarevok
Would it make sense to put it into its own table first or? I really dunno
2023-03-17 07647, 2023
bitmap
I think so. we only need a private, single-column table for this. and that makes it easy to provide a 'slow' fallback if the table doesn't exist on mirrors, because it's trivial to write a view that provides the same interface
2023-03-17 07621, 2023
reosarevok
I'm not sure how and how often triggers should run - I guess we should never get an editor *into* the table once it gets out of it
2023-03-17 07658, 2023
reosarevok
(It seems a bit wasteful to run a trigger after any edit is entered, and we'd have to what, run a trigger every day too to update the X days old bit?)
2023-03-17 07659, 2023
Lotheric joined the channel
2023-03-17 07613, 2023
bitmap
I don't think the X days old bit can be materialized with triggers. but the slow bit is likely the edit count calculation, so we'd need something like the edits_* columns we used to have in the editor table, but in a separate table
2023-03-17 07650, 2023
bitmap
anyway, we should at least try to see if the query plan can be improved without adding more tables first
2023-03-17 07617, 2023
reosarevok
Do you have any ideas for that? :) There's no huge rush with this but if you want to play with explains at some point I'm not going to complain :D
2023-03-17 07641, 2023
jivte__ has quit
2023-03-17 07637, 2023
bitmap
no, since I haven't seen the query plan yet:P
2023-03-17 07642, 2023
bitmap
maybe I can look into it next week
2023-03-17 07654, 2023
reosarevok
Sure
2023-03-17 07600, 2023
reosarevok
Zero rush
2023-03-17 07629, 2023
texke has quit
2023-03-17 07652, 2023
zas
lucifer: I reclaimed a bit of diskspace on gaga (deleting few caches & logs), there's an unused docker volume named listenbrainz-timescale-data (667.5GB), can you check?
2023-03-17 07633, 2023
Pratha-Fish
Hi reo, so I've been working on adding ISO codes in the bot, and I've ran into a little issue
2023-03-17 07624, 2023
Pratha-Fish
When I try to add a random ISO 3166 code for testing purposes, it (rightfully) claims the code doesn't exist. To tackle this, I've been using real world codes from https://en.wikipedia.org/wiki/ISO_3166-3. However, when I use real codes for areas that are already added, it throws an error "An area already exists with this ISO code" https://usercontent.irccloud-cdn.com/file/Z9NnCNj…
2023-03-17 07631, 2023
Pratha-Fish
^ reosarevok
2023-03-17 07617, 2023
Pratha-Fish
I have added a feature to include these ISO-codes when adding areas using the bot, but I haven't been able to verify if the newly generated area includes these ISO-codes or if it ignores them due to error mentioned in the above screenshot
2023-03-17 07650, 2023
lucifer
zas: yes, that volume can most probably be removed. let me confirm once with mayhem or alastairp?
2023-03-17 07659, 2023
reosarevok
Pratha-Fish: what's the actual error when making things up?
reosarevok: That's smart! Let me check if it works
2023-03-17 07628, 2023
Pratha-Fish
reosarevok: sooo it looks like when I run the bot while specifying the ISO code, it generates a new area WITHOUT the ISO code. However, when I try to edit the area and enter the said imaginary ISO 3166-1 Code, it accepts it without any issue
2023-03-17 07655, 2023
Pratha-Fish
It seems I am doing something wrong on the bot side.
2023-03-17 07651, 2023
iconoclasthero has quit
2023-03-17 07601, 2023
iconoclasthero joined the channel
2023-03-17 07617, 2023
Sophist_UK joined the channel
2023-03-17 07649, 2023
Sophist-UK has quit
2023-03-17 07609, 2023
Pratha-Fish
reosarevok: so I assumed adding the above codes using our bot should be as simple as finding the name of the text box using Dev Tools, and setting a value to that control using ```self.b["control_name"] = "some_value"``` https://usercontent.irccloud-cdn.com/file/FrjtsuD…
2023-03-17 07655, 2023
Pratha-Fish
But apparently mechanize doesn't recognize the names for these 3 text boxes, while it does for other text boxes like name, disambiguation, etc.
2023-03-17 07646, 2023
reosarevok
Oooh
2023-03-17 07651, 2023
reosarevok
That's because they are multiple-boxes
2023-03-17 07657, 2023
reosarevok
Probably
2023-03-17 07647, 2023
reosarevok
So the name of that first input is edit-area.iso_3166_3.0
2023-03-17 07603, 2023
reosarevok
Are you setting the 0?
2023-03-17 07613, 2023
mayhem
ok, good board meeting in the bag. thanks for your help on that reosarevok
2023-03-17 07615, 2023
reosarevok
If you are, maybe something else needs work (maybe on the bot, maybe on MB)
2023-03-17 07605, 2023
Pratha-Fish
reosarevok: Yes, I am setting the names correctly. However to see it in detail, I opened up a debugger to see what names and controls mechanize recognizes in the first place.
2023-03-17 07639, 2023
Pratha-Fish
Mechanize seems to recognize these 3 boxes, but it doesn't recognize their names. However, it assigns index numbers to each of these controls
