#metabrainz

[listenbrainz-android] 14dependabot[bot] opened pull request #405 (03dev…dependabot/gradle/dev/com.android.tools.build-gradle-8.4.0): Bump com.android.tools.build:gradle from 8.3.2 to 8.4.0 https://github.com/metabrainz/listenbrainz-andr...

[listenbrainz-android] 14dependabot[bot] opened pull request #406 (03dev…dependabot/gradle/dev/io.sentry.android.gradle-4.5.1): Bump io.sentry.android.gradle from 4.4.1 to 4.5.1 https://github.com/metabrainz/listenbrainz-andr...

[listenbrainz-android] 14dependabot[bot] closed pull request #397 (03dev…dependabot/gradle/dev/io.sentry.android.gradle-4.5.0): Bump io.sentry.android.gradle from 4.4.1 to 4.5.0 https://github.com/metabrainz/listenbrainz-andr...

yvanzo: bitmap: reosarevok: This has slipped under my radar a bit - could the blog post mention in it that we don’t allow titles over x length any more? And what the style guidance is for truncating? Those are the things our editors will want to know imo

monkey[m]: I'm getting an error while connecting to spotify on test.lb. https://usercontent.irccloud-cdn.com/file/6MUmL...

It is working perfectly on beta and pod

[listenbrainz-server] 14anshg1214 closed pull request #2639 (03master…listening-queues): Add Listening queues to BrainzPlayer https://github.com/metabrainz/listenbrainz-serv...

https://x.com/grrrlsgovile/status/1785336814699... 😔

let the enshittification of spotify continue!

since growth is no longer on the books, its time to put the squeeze on the users.

Ooh GSoC results today? According to Twitter

yep. :)

Exciting!

of course we know the answers already. :D

I don’t haha. No spoilers!!

p.s. I want to share this shortened track title MB server fix to our socials, but I think it would be cool to add style guidance first, if there is any, when you’re on reosarevok

It's a holiday, aerozol! :D

Ooh, happy holidays!!

Oh shit, gotta send my invoice

mayhem: same ^

re aerozol, cc reosarevok: On “complaints”, I’ve rather read that they enjoy the bugs they trigger, it is literally written in their “title”. They are specifically targeting online music platforms and databases.

re aerozol, cc bitmap, cc reosarevok: On “the blog post”, this change is already mentioned in the ticket’s title which is listed once and linked twice. It isn’t impacting anyone but mostly trolls and a very few mistaken editors (one every four years on average). Last, we don’t want to give trolls the effect/visibility they seek to obtain, so keeping low profile on this is just fine. For the same reason, I won’t spend any more

time about this topic.

[14:33] <reosarevok> Well, we're not going to add a guideline saying titles should be short, because I strongly disagree with that idea, long titles are a valid artistic choice :)

[14:33] <reosarevok> We can document that we have a maximum limit for technical reasons, that's it

I agree very strongyl here (and also i would like to wor kagaisnt the database limit in the future)

hm..

hmm

mayhem: anything particular you would like me to work on?

I was under the impression that this was going to be temporary until (at some time) we fix the underlyig issue. that fixing wasn't exactly top priority since the issue was rare and not often showing up

but sillyname names are valid?

sure sometimes it's to poke a box to see how many charas show up

but I can even think of valid situiations where eg an AC would be long af witouth it being to "troll" someone

<aerozol> "Exciting!" <- and nervous 😅

i really really think we shouldn't put the breaks on AC lenght in full!

not being top priority to fix is fine. but it shoudl eventually be reverted so longer text titles and the like can be added as before

is this trolling? https://beta.musicbrainz.org/release/34b47db4-a... ?

maybe?

lucifer: top recordings for artist API endpoint?

👍

or, better yet, pick a task from the planning doc. :)

[data-set-hoster] 14amCap1712 merged pull request #17 (03master…dependabot/pip/pydantic-1.10.13): Bump pydantic from 1.10.8 to 1.10.13 https://github.com/metabrainz/data-set-hoster/p...

I guess yvanzo doesn’t want to talk about it, but is he expressing thoughts of a lot of people, in discussions that I’ve missed? Maybe with bitmap?

FWIW I’m sure some people are vandals/trolls. I don’t really care about them, f*ck them - I just want to have robust communications for the editors (that we do care about) who put time into editing and will be effected or run into this eventually. But I can bow out if it’s not helpful, this seems like a spiky subject

zas, atj, since you debugged the weird ipv4 openssl issue with me last time: just as I was about to summarize our findings in a forum post, I came to realize that the issue has resolved itself in the meantime.

there was no openssl update since then, so that probably wasn't it, but I also don't want to spend any more time on this, so I'll just treat it as a fluke and move on

FichteFoll: thanks for the update. Glad it's resolved. What a strange issue!

aerozol: I only really discussed it in the pull request (and briefly on IRC when I was finding statistics on title length). I did propose increasing the allowed length further (or allowing auto-editors to bypass the restriction), but was mainly concerned with preventing the replication/dump issues for now.

yvanzo: sorry I had seen your ping about the blog post, but then got distracted and failed to review it -- thanks for posting it anyway

derat: that's true, I think it should be possible to encode those fallbacks in the sql query, but we'd still need to keep the perl implementation for the search code which is kinda annoying

ansh: thanks for reporting. I'm out and about today but will look tomorrow. I don't remember what's running on test

Right now, it's the huesound refactor PR

I see. Yeah, a tomorrow problem :D

ansh (IRC): Just tried on test.LB, was able to connect to Spotify. Maybe related to our rate limit issues with the spotify api? Not sure what happened there

I tried again, and got the same error

Congratulations everyone who’s selected!!

ericd, JadedBlueEyes, kellnerd, pranav, rimskii, theflash_, twodoorcoupe, yellowhatpro: https://blog.metabrainz.org/2024/05/01/welcome-...

congrats all :)

congrats guys!

congrats everyone 🥳

I didn't get accepted 😔

It's been good knowing you monkey , lucifer (IRC)

congrats yall!

* Congrats to everyone who's selected.

Unfortunately, I didn't get accepted 😔

It's been good knowing you monkey , lucifer (IRC)

congratulations to everyone who got accepted!

would really like to know what went wrong with my proposal if that's possible, for future experiences

huhridge: Ya, me too

Congrats everyone! This just feels surreal

<07munishk> Congrats everyone!!

Congrats !

feeling so happy haha

<10avamander> Gratz

aerozol: I mean I totally get that. the vandals/trolls are annoying for sure.

personally I don't *care* and want to just fix it so their attempted breakege does nothing.. somehow having to truncate titles just feels like concession a bit (as well as possible "valid" uberlong titles having an issue)

Well done to everyone that participated this year, and congratulations to those who got selected!

We had lots of quality proposals this year 👏

I did propose increasing the allowed length further (or allowing auto-editors to bypass the restriction),

interesting idea..

Congratulations to everyone who made it this year and my best wishes for all others, next year is your chance to come back with an even stronger proposal!

I remember 2 years ago that there was one person rejected, not based on thier proposal being off but simply becasue there wasn't enough spaces

so it might be tha huhridge

Thanks MetaBrainz for giving me the chance to continue last years project!

number of slots allotted by google plays a major role i guess

it does actually! it's hard for the mentors to pick when so many god proposals

good*

Definitely, if I correctly understood the procedure correctly, the organization does not know beforehand how many students they get, they can only rank proposals.

Congratulations everyone!! ❤️🔥

I confirm it's hard every year to select a limited amount of proposals, and heart wrenching at times

but from experience i can tell you that anyone not had theri proposal accepted: STAY, stay for a year and get to know us even more, get editing, get bugfixing, and then the chance is very, very high that nex year you will be accepted

aerozol: If you do share about the MB Server hotfix on our social networks (I’m not sure that it is timely anymore), please don’t let it shade the happiness of these much better news: https://blog.metabrainz.org/2024/05/01/welcome-... 😄

I also got rejected but its fine, in these past months I got to learn so much... maybe next year 😁