Notes from #MetaBrainz Meeting 2025-02-17

[aerozol]

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs
Meeting wiki page: MetaBrainz Meeting - MusicBrainz Wiki

Agenda

• Reviews
• SSO

Last meeting: 2025-02-10
Next meeting: 2025-02-24

@reosarevok: Welcome to another MetaBrainz Monday Meeting!

Reviews

@derat

[mailed in] My fixes for MBS-13920 went in – thanks to reosarevok and bitmap for reviewing!
[MBS-13920: Make it harder to skip warning about feat. artists in track titles]
I also started messing around with Tidal’s complicated and poorly-documented v2 API since most of yambs’s requests to their internal API seem to be getting blocked now.
It feels like they’ve done their best to make it hard to use from a statically-typed language (e.g. properties that can be either an object or an array of objects, arrays that mix objects of different types), so we’ll see if I have the patience to actually rewrite my code to use it.

@aerozol

[mailed in] I am feeling better now, just having a fun time trying to catch up on sleep and two weeks of neglected work. If I’m up I’ll pop into the meeting, but if I am getting some blessed sleep I will take it, and you will see me at next week’s meeting.
Same as last week, I have just been staying on top of the basics, socials and a couple of tickets.

@ApeKattQuest_MonkeyPython

[MonkeyPython] Still having very hectic weeks (and due to house BS going to be EVEN Moar this week)
not helped by there being an emergency cut of the water for 2 hours this morning due to some pump-error (was thankfully fixed atleast)
Still I am starting to see the end of the Work on the Table of Contence for our BookBrainz Style document (I hope, I keep finding new things we should probably add, lol)
updated Vivaldi (shock gasp!) so now translations don’t work anymore, lol (translating work on Picard will have to eh, wait.)
In that vein: anyone familiar with vivaldi/chrome extensions who want to earn 100 bucks get in contact with me abt writing a gorram extension. (I’ve had it, lol)
There’s more of this stuff, but it’s offtopic so not important
Come March and I’ll have time to work on instruments again (hopefully, lmao)

@kellnerd

I’ve also been in the “annoyed by Tidal’s API” team this week
I was testing and reviewing outsidecontext’s provider implementation for Harmony, trying to make the best out of what we have…
[github discussion] is probably a good summary why it is annoying to use.
At least I also found a bit of time to also do a bit of coding and community support as well.

@zas

Last week we received new AX102 servers, I configured them. Those are named cesaria & isaac, they are aimed at replacing our current main db servers ASAP.
I continued to work on the DNS migration; wrote a script to ease export/import from Gandi to Porkbun, currently testing, we created accounts, and we’ll start very soon, with few non-critical domains
Plus usual stuff, supervision, admin tasks, upgrades, Picard PR reviews (about that, we released a new version of Picard 2.13 today).

@bitmap

last week I worked on some infrastructure related tasks, mainly setting up new PG standby nodes on cesaria/isaac, moving all test.mb services to another node, updating docker-postgres-cluster/syswiki
I also worked on some minor MBS tickets and got CI (very nearly) passing in my github-actions branch after fighting with chrome for several hours
also did a bunch of code review

@outsidecontext

last week I looked into the packaging issue we had with the recent Picard release and for which zas and I did the release today. Also some bugfixes.
I also started looking into the macOS ARM builds again, I think we will have some test builds for interested users soon
Apart from that finished the Tidal implementation for Harmony. It’s currently in kellnerd 's thorough review : ) We should have this ready soon

@anshgoyal31

[ansh] Last week, I started working on the recordings page.
I explored the options to migrate LB from Bootstrap 3 to React Bootstrap 5.
Fixed stuck Server CI Tests.
And reviewed couple of PRs.

@mr_monkey

[monkey] Last week I started work on fixing LB-1659, and issue with listens submission
[LB-1659: Brainzplayer partially sends the information of the previous track instead of current]
(And more generally stale state in BarinzPlayer)
Or, you know, spelled correctly
Had meetings with the LB team
Worked on adding the new playlist cover images to the playlist overview page
Reviewed PRs and followed up on user feedback
Reviewed BookBrainz PRs and worked on the bootstrap5 migration a bit
And finally, implemented LB-1735 as a little gift for aerozol
[LB-1735: Manually add listens: Default to MBID type being pasted]

@yvanzo

Not much about last week, I just kept working on MusicBrainz Solr 9 backups.

@Gautam_coder

[GautamShorewala] Last week was not well so not able to do much
My mr for orientation issues in LB was merged
So hopefully it will improve user experience in tabs
And currently looking into some issues I can work on

@rob

[mayhem] last week was the usual background stuff, emails, customers etc.
but then I switched to doing technical work – first try to convince Solr to do typesense style spelling correction and the results are… confounding. i’ll have to ask lucifer to take a look at it and see if he can spot something else.
but that endpoint is getting over 500k requests per day, so its not trivial.
and then I started working on listenbrainz-local and made very good progress. hopefully next week I can have something to show off for people who have a subsonic API installation. fun stuff.
and a big thanks for lucifer for helping me with the OAuth client stuff – saved me lots of time.

@lucifer

This week I worked on getting a bunch more old PRs ready for merging
A lot of small tickets, including a bunch of URL stuff as usual
Dealing with a good bunch of reports, a few new style changes, and then I got sick so I’ve been taking it slow today

@julian45

This week I tested one of the SSO tools up for consideration within my lab environment and adjusted the doc I wrote accordingly – re-ranked some things and wrote up a proposed action plan.
Hopefully in the slot after reviews, we can do a quick recap and come to a decision about action steps.
(refresher: link is here: [google doc]
if you have looked at the doc before, you should be able to see changes since your last view, at least in a web browser)

@jasjeet

[jasje] Did some PR reviews last week
Re-iterated on potential projects

SSO

@julian45

So first, a refresher on motivation and general aims of this work:
The idea is to implement a centralized identity provider for MeB admins/staff and use single sign-on (SSO) integrations with as many services as possible that support it, such as MeB’s Google Workspace tenant, Sentry, etc.
This both reduces the amount of credentials that need to be remembered for each user down to 1 (or as close to it as possible) and centralizes the ability to audit/log user auth history, as well as use more modern auth like passkeys and time-based keys and the like
Some tools are identified and discussed in the doc but reducing my proposal down to its most fundamental parts:
Step 1: Try the self-hostable tool that came out in 2nd place first since it deserves a fair shot (didn’t quite beat another tool since it misses something the other one does natively, but is lighter-weight than that other one)
Step 2: Should that not work out, try the other main self-hostable candidate
Step 3: If at any point it becomes too much trouble/time/effort to self host this, consider some of the closed-source/commercial options discussed in the doc. Hopefully it doesn’t come to this
At all points, we would start with a small test group of users to minimize efforts if moves between tools are necessary…
And then for each tool that the group evaluates, we consense on go/no-go for that tool and either continue to the next one to try or expand the user tool as appropriate
Decision tree cycles as needed until the best tool for us is found.
Alright that’s most of what I wanted to put out there.
For today: can we decide yes/no about the proposed action plan?

It is agreed to run a test. Quite a bit of related chat, please see the logs for more.

Absent: nobody!