[listenbrainz-server] 14dependabot[bot] opened pull request #3423 (03master…dependabot/npm_and_yarn/mdast-util-to-hast-13.2.1): chore(deps): bump mdast-util-to-hast from 13.2.0 to 13.2.1 https://github.com/metabrainz/listenbrainz-server…
2025-12-02 33610, 2025
_BrainzGit
[bookbrainz-site] 14dependabot[bot] opened pull request #1206 (03master…dependabot/npm_and_yarn/nodemailer-7.0.11): chore(deps): bump nodemailer from 7.0.7 to 7.0.11 https://github.com/metabrainz/bookbrainz-site/pul…
[listenbrainz-server] 14dependabot[bot] opened pull request #3424 (03master…dependabot/pip/werkzeug-3.1.4): chore(deps): bump werkzeug from 3.1.3 to 3.1.4 https://github.com/metabrainz/listenbrainz-server…
Hi! I’m Sejal, and I’m interested in contributing to ListenBrainz under MetaBrainz for GSoC 2026.
2025-12-02 33612, 2025
Sejal_28
I work with Python, data analysis, APIs, Git/GitHub, and basic backend/testing.
2025-12-02 33612, 2025
Sejal_28
I’d appreciate any guidance on where to begin or which starter issues to look at.
2025-12-02 33622, 2025
Sejal_28 has quit
2025-12-02 33649, 2025
julian45[m]
[lucifer](https://matrix.to/#/@lucifer:chatbrainz.org): had this thought right before going to bed, so might not be fully formed, but i wonder if we might be able to sidestep some the persistence issues with matrix-appservice-irc on the chatbrainz server (assuming part of the issue is connecting to ports exposed by particular containers) by adding an extra argument publishing ports from those containers on the host in a way that the
2025-12-02 33649, 2025
julian45[m]
nspawn'd container can see but doesn't expose those ports to the world, if that makes sense
2025-12-02 33645, 2025
Sejal_ has quit
2025-12-02 33628, 2025
s1b1 has quit
2025-12-02 33655, 2025
s1b1 joined the channel
2025-12-02 33602, 2025
FaizanAkhtar[m] joined the channel
2025-12-02 33603, 2025
NOTICE: LB-1880 (https://tickets.metabrainz.org/browse/LB-1880): Save listens and retry if submission fails in BrainzPlayer
2025-12-02 33603, 2025
FaizanAkhtar[m]
Hi monkey following your advice i found a new task... LB-1880 (Save listens and retry if submission fails ) ... i think this is suitable for me to work on ..!
julian45: if i understand that is what the conflicting changes do. let me know when you are around and we can take a stab at it. iiuc the ports were never exposed to the world just on the host for nspawn'd container.
2025-12-02 33631, 2025
_BrainzGit
[listenbrainz-server] 14faizanakhtar123 reopened pull request #3421 (03master…fix-lb-1622-tag-input): LB-1622: Prioritize user input over suggestion on tag creation https://github.com/metabrainz/listenbrainz-server…
NOTICE: LB-1622 (https://tickets.metabrainz.org/browse/LB-1622): Use the user input when adding a tag with the "Enter" key
2025-12-02 33613, 2025
aerozol[m]
Jade: the compatibility graphs have not been very good for a while now. I don't think it's an error, just how they are calculated. A lot of users will only have people at a few percent max
2025-12-02 33640, 2025
aerozol[m]
No offence to whoever coded them - iirc they were changed to fix some other problem, and now we have this problem. So it goes :)
2025-12-02 33601, 2025
aerozol[m]
Not sure if related, this seems like an actual bug though: LB-1569
NOTICE: LB-1569 (https://tickets.metabrainz.org/browse/LB-1569): Compatibility meter is broken?
2025-12-02 33658, 2025
x123 has quit
2025-12-02 33621, 2025
aerozol[m]
Ooh, YiM 25 in progress! Let me know if you could do with anything more from me monkey
2025-12-02 33624, 2025
aerozol[m]
I really like your AI blurb reosarevok! Still a bit woozy, but I'll have an edit. And then you can take or leave my changes
2025-12-02 33650, 2025
reosarevok[m]
Not mine, monkey's :)
2025-12-02 33654, 2025
reosarevok[m]
But no rush
2025-12-02 33620, 2025
aerozol[m]
Oh, indeed! I really like it! I have only shortened it because people don't like to read... the shorter the more chance of reading. Though I guess these users will get an LLM to summarize the page anyway /laugh /cry
2025-12-02 33632, 2025
aerozol[m]
My quick edit:
2025-12-02 33635, 2025
aerozol[m]
Undisclosed use of AI or Large Language Models, or inability to explain AI-generated contributions, will lead to your PR being closed without further review.
2025-12-02 33635, 2025
aerozol[m]
You may use LLM as part of your workflow, but the understanding the issue and any problem solving should be done by you. This is the core of our work as developers. The job market and financially motivated projects may not agree with this, but this wonderful little open-source bubble has a humanistic philosophy, and prioritizes community, critical thinking and robust and long-lasting code over productivity and speed.
2025-12-02 33655, 2025
aerozol[m]
Maybe even just "Any inability to explain AI-generated contributions will lead to your PR being closed without further review."
2025-12-02 33601, 2025
aerozol[m]
In the first line
2025-12-02 33600, 2025
aerozol[m]
This next one might be for you lucifer? Unless the issue is on the LB side/how it's sending people to MB - then it might still be you I guess ;)
2025-12-02 33611, 2025
aerozol[m]
https://elk.zone/mastodon.social/@tagomago/115646… - "@metabrainz Hey!! 👋 I saw a strange loop where I couldn’t log into my ListenBrainz account via MusicBrainz IF I‘m using the MB beta site. Going back to the regular MB site grants me access again 🎧 🤔"
2025-12-02 33633, 2025
aerozol[m]
I replied with - "Thank you for reporting! I was able to recreate this and went to make a ticket, but apparently I already reported this months ago :P https://tickets.metabrainz.org/browse/LB-1792 Now that a user/fellow MB beta user has also reported it, I will nudge some people to get it fixed. We are working on an OAuth overhaul, so if it conflicts with other work we ask and thank for your patience -a"
2025-12-02 33634, 2025
BrainzBot
LB-1792: Can't log in to ListenBrainz if on MusicBrainz Beta
2025-12-02 33635, 2025
NOTICE: LB-1792 (https://tickets.metabrainz.org/browse/LB-1792): Can't log in to ListenBrainz if on MusicBrainz Beta
2025-12-02 33612, 2025
aerozol[m]
Thanks for the heartwarming story link mayhem. Very nice! Shared on our socials as well
2025-12-02 33644, 2025
s1b1 has quit
2025-12-02 33638, 2025
s1b1 joined the channel
2025-12-02 33645, 2025
reosarevok[m]
bitmap: Took on MBS-14201 (which was assigned to you) since I know you're busy, hope you don't mind
[listenbrainz-server] 14MonkeyDo merged pull request #3421 (03master…fix-lb-1622-tag-input): LB-1622: Prioritize user input over suggestion on tag creation https://github.com/metabrainz/listenbrainz-server…
NOTICE: LB-1622 (https://tickets.metabrainz.org/browse/LB-1622): Use the user input when adding a tag with the "Enter" key
2025-12-02 33647, 2025
monkey[m]
lucifer: A user reported the link listens isn't updating, and I was able to confirm for my own page. It had worked when you ran it manually, but did not run last week according to the schedule. (https://mastodon.social/@okwithmydecay@en.osm.tow…)
2025-12-02 33647, 2025
monkey[m]
Is that related to issues we were having with disk space / nuking the dump?
2025-12-02 33653, 2025
_BrainzGit
[listenbrainz-server] 14faizanakhtar123 opened pull request #3426 (03master…fix-lb-1880-retry-logic): LB-1880: Implement localforage persistence for unsent listens. Fixes … https://github.com/metabrainz/listenbrainz-server…
NOTICE: LB-1880 (https://tickets.metabrainz.org/browse/LB-1880): Save listens and retry if submission fails in BrainzPlayer
2025-12-02 33605, 2025
reosarevok[m]
Hmm. I see the new redesign has `Email: support@metabrainz.org` on the footer. mayhem: IIRC we specifically hide our email further for a reason, was it spam or?
2025-12-02 33633, 2025
ApeKattQuest
I mean as an user i hate whne email is hard to find on sites...
2025-12-02 33652, 2025
ApeKattQuest
but we could obfuscate it in some way to prevent bots
2025-12-02 33630, 2025
mayhem[m]
reosarevok[m]: I don't recall. but I'm sure it doesn't really make a difference these days, does it?
We have advertising@metabrainz.org as the "big email" and then the support email is behind the "I have read that we don't sell stuff, license stuff and hire people" disclaimer
2025-12-02 33613, 2025
reosarevok[m]
To be fair, we do still get a bunch of people asking about all those three things anyway
2025-12-02 33622, 2025
reosarevok[m]
I had genuinely forgotten we have a merch shop thing
2025-12-02 33657, 2025
mayhem[m]
I should shut that down. I think we sold one t-shirt. To Bob switft, IIRC. despite a bunch of people clamoring for shirts back in the day
2025-12-02 33614, 2025
reosarevok[m]
I mean, a fair amount of people might also never have found out
2025-12-02 33628, 2025
reosarevok[m]
And a bunch of us get them for free every year 😅
2025-12-02 33632, 2025
reosarevok[m]
But yeah, dunno
2025-12-02 33654, 2025
reosarevok[m]
bitmap, ansh: left a bunch of comments now, mostly on caps, indents and i18n stuff
2025-12-02 33623, 2025
reosarevok[m]
ansh: take a look at `exp.l()`, it will help with a bunch of now dodgy translatable bits :)
2025-12-02 33646, 2025
reosarevok[m]
I'll check further stuff tomorrow, I see bitmap is busy improving things rn as well
2025-12-02 33650, 2025
bitmap[m]
thanks, sorry if my recent pushes conflicted with any of the proposed changes
2025-12-02 33623, 2025
bitmap[m]
(was also fixing i18n stuff in a couple files)
2025-12-02 33647, 2025
reosarevok[m]
No, I was in index.js mostly and the footer which I think you didn't touch yet?
2025-12-02 33611, 2025
bitmap[m]
ah yeah, I only touched navbar and editor-tools
2025-12-02 33611, 2025
reosarevok[m]
I also sent a quick extra commit removing double newlines that you added to a couple files, ansh - to be fair we're not super consistent with those
2025-12-02 33623, 2025
reosarevok[m]
But we mostly seem to avoid it, so let's not introduce more
2025-12-02 33621, 2025
reosarevok[m]
Unrelatedly, I know I'm not discovering anything new, but most Gondwana Records stuff is pretty neat for working
2025-12-02 33630, 2025
reosarevok[m]
I'm actually surprised we don't have an eslint rule to avoid double newlines, actually
2025-12-02 33640, 2025
reosarevok[m]
... actually.
2025-12-02 33645, 2025
bitmap[m]
reosarevok: let's try to add [ci ckip] to future commits where appropriate (I expect they'll be squashed later), since all these CI runs waste a lot of time and electricity
2025-12-02 33601, 2025
bitmap[m]
* reosarevok: let's try to add \[ci skip\] to future commits where appropriate (I expect they'll be squashed later), since all these CI runs waste a lot of time and electricity
2025-12-02 33605, 2025
reosarevok[m]
Oh, I didn't know that was a thing!
2025-12-02 33613, 2025
reosarevok[m]
How does it work, just have that somewhere in the commit message?
2025-12-02 33607, 2025
bitmap[m]
I think so (I haven't used it yet either and have been canceling them manually, just proposing it now :))
NOTICE: LB-1867 (https://tickets.metabrainz.org/browse/LB-1867): LibreFM-compatible CSV exports may not have comment lines
2025-12-02 33655, 2025
Sejal_ joined the channel
2025-12-02 33646, 2025
Sejal_ has quit
2025-12-02 33606, 2025
julian45[m]
<lucifer[m]> "julian45: if i understand that..." <- IIRC, the extra command line args we supplied in MDAD that were persistent before (but don't work now because of docker engine updates) were for pinning the *IPs* of a couple containers, not necessarily for ports. i'm hoping that if we can get specific, easy-to-ID ports (e.g., unusually high number and/or written down somewhere easily referenceable) for the necessary docker
2025-12-02 33607, 2025
julian45[m]
containers exposed within the host, we can just have the nspawn'd container talk to `localhost` (or the rough equivalent) at those ports and thus not need to worry about pinning the container IPs
