#metabrainz

macarena

not much from me -- I mostly kept up with emails and continue to monitor cron jobs to make sure they check-in an all that. lots of weird debugging but most of them are happy now.

this coming week is going to be super busy for me. but that is it.

fin. @zas?

zas: that is.

Hey

Still on my list for today: yellowhatpro, ansh, kellnerd, aerozol, atj, julian45, outsidecontext, lucifer, jasje

The week before Christmas I spent some time analyzing web logs and blocking some abusers that were ignoring rate limits

Then only usual supervision, Picard PRs reviews (quite a lot of PRs opened by outsidecontext), upgrades, and enjoying time with family & friends.

That's it. aerozol ?

Last few weeks were mainly Year in Music

I didn’t quite know what to do so I mucked about, and then we thought about seasons, and then suddenly it became 4x the work

But was very fun tbh, and been enjoying watching the feedback roll in

I think LB is starting to, slowly, gain some mass

Over Christmas? Sounds appropriate

So did I

Died from not laughing just now

Jokes, had a lovely break. Did quite a few things but didn’t really keep track

A lot of editing which has been really nice! Been a while

Gooooo ansh

Hi Everyone!

Last 2 weeks, I was working on building a Genre Explorer for LB.

Fixed some bugs In TROI for Apple Music exports.

Worked on Year in Music and created a new Genre Graph this time.

I continued working on improving the playlist page and building a playlist cover art.

And fixed a couple of bugs on the UI front and reviewed some PRs.

That's it for me.

lucifer: next?

ansh[m]: What *is* a genre explorer?

Sounds exciting

hi all!

Ok, he arrived, tell me later :)

Continue, lucifer!

Still on my list for today: yellowhatpro, kellnerd, atj, julian45, outsidecontext, jasje

in the past weeks, i worked on deploying Year in Music and debugging a couple of related issues. also worked on finding ways to speed up the processing of stats in spark cluster.

and making our apis less prone to CORS errors.

that's it for me. kellnerd next?

Hi all!

During the last weeks I've only been working on some minor improvements for Harmony.

Mainly solving the issue of merging artist credit arrays and their external identifiers even if they are not in the same order or spellt differently.

I finally started to write more BDD tests for some utilities and looked into creating some helpers to write dry provider tests (without doing network requests!)

And I spent the last two days of the year to submit my missing 2024 listens from .scrobbler log files and handwritten notes to get the best out of YIM :)

That's it, go julian45!

kellnerd: Please try again!

Hmm, go jasje!

Hi all! I ended up taking the last couple weeks to spend a lot of time with family - unfortunately this has meant little productivity in both MB and other respects. That being said, I am now back to it and ready to work on the things I said I would work on - apologies for the delays this has created.

That's all for me

Ill go automatically

Last week

julian45: oops, I had seen that you were supposed to be there, but no Matrix typing indicator...

Actually last weeks ive been recovering from a viral

So could do much but review PRs

Gautam Shorewala: and Shreyas: have been doing some heavy lifting and bringing in interesting changes

* Actually last two weeks ive

Brainzplayer is getting better with minor UX quirks being solved

Apart from that, this yesr we might not be doing yim on the app side

s/yesr/year/

But discussions are open if someone wants to pick it up :)

YIM is in the past my friend ;P

Thats it for me

Whos left?

outsidecontext:?

Still on my list for today: yellowhatpro, atj, outsidecontext

Any of those can go, if around :)

Same list with handles: yellowhatpro, atj, outsidecontext

atj: ?

Shreyas: want to go?

Hi

So for the past few days I was working on brainzplayer

Implemented couple of features

Solved some bugs

Got reviewed by jasje:

He is helping me to implement the features

That's it for me :)

Hi lazybookwyrm; do you want to go?

Shreyas: should I add you to the weekly list? :)

Same for all the other new contributors for LB!

And Android LB

reosarevok[m]: Yes please :)

I would love to come

Done!

Gautam Shorewala: you can go after lazybookwyrm:

* @gautam_coder:matrix.org: you can go after lazybookwyrm:

👀 I haven't done anything, why am I getting mentioned lol

Do something quick

Make a joke

lazybookwyrm, never mind, I thought that you were typing.

It's fine :)

Discord does that sometimes when you enter a channel and accidentally hit the keyboard lol

Gautam Shorewala: all yours then :)

Hi all

Last few days I have been looking into the listenbrainz player

Fixing bugs

Implementing new ideas

Trying to improve existing features

That's all

:)

Bang time?

The html one?

Thanks everyone!

And here I thought reosarevok was running the meeting...

Ok, I *think* that completes the reviews, unless Bob Swift wanted to give one :)

So, thanks everyone!

No review from me. Thanks.

Reminder, we are meeting next week, no more two-weeks-off for you! You better do stuff! 😉

While we're here, happy new year everyone !

Ah, yeah, Happy New Year for those who Gregorian!

While we're here, happy new year everyone !

</BANG>

(the html kind)

ansh: so what's this explorer? Does it have a hat and a monocle?

Heya Gautam Shorewala , what’s your MB username? For the meeting minutes

I didn't want to disturb the meeting, so I waited until it was over. Speaking of OAuth... It appears that MusicBrainz is no longer accepting HTTP Digest authentication for adding or removing items from personal collections. I have a local app I developed to manage my local music (albums, CDs, digital downloads, etc.) that updates me collection on MB. It worked fine until about a month ago, so I assumed it had something to do with

the switch to OAuth. I ended up registering my local application and revising it to use OAuth to get it to work again. Not a big deal, but if HTTP Digest is no longer supported, the documentation at https://musicbrainz.org/doc/MusicBrainz_API should probably be updated accordingly. I suspect this will also ultimately impact the python 'musicbrainzngs' module.

s/me/my/, s/MusicBrainz_API/MusicBrainz\_API/

reosarevok[m]: LB-1509. So I am creating a graph, where every node represents a genre, and they're connected to other genres based on their relationships. So, the users will be able to discover new genres, and also get recommendations on some artists or albums.

LB-1509: Genre explorer https://tickets.metabrainz.org/browse/LB-1509

I don’t know if you guys already have plans ansh and monkey but after this it would be cool to look at surfacing more of our existing features into user pages and feeds. We have a lot of cool stuff now, that not a lot of users know about/use!

Oh, neat!

The explorer, not the auth issues. bitmap, lucifer, please look at what Bob Swift asked above :)

<aerozol[m]> "Heya Gautam Shorewala , what’s..." <- Gautam_coder

yellowhatpro: that’s three in a row you’ve been away for btw, I removed you from meeting regulars to ease the process. Let me know if you’re around again and I’ll add you again, or feel free to add yourself again any time :)

Bob Swift: hi, I don't believe we made any changes that would affect digest auth (though I could be wrong). I tested it using `curl` just now and it seems to be working for me

one case where digest auth is known to break is when someone renames their account, but I assume that was not the case for you

Definitely stopped working for me, and I didn't rename the account. Not sure what happened, but I've rewritten my app to use OAuth so it's working fine now.

ok, I'll test it again with adding/removing to collections specifically

I don't know if it makes a difference, but mine is using a collection of releases.

And I was actually logged into MusicBrainz at the time, although I'm not sure that matters.

The response I received using my usual user id and password (hard coded into my app and worked perfectly until about a month ago) was:

JSON: {'help': 'For usage, please see: https://musicbrainz.org/development/mmd';, 'error': "Your credentials could not be verified. Either you supplied the wrong credentials (e.g., bad password), or your client doesn't understand how to supply the credentials required."}

odd, with my account, adding/removing to a release collection (while logged in) is also working. have you checked if it fails using curl or on test.musicbrainz.org too? also, do you know which day it stopped working on? I can check if there was some sort of server update.

I haven't checked using curl, and I don't know when it actually stopped working. The last time I used it was around the beginning of December and it worked then. When I tried using it this weekend, I kept getting the response above. I just assumed it was because of the OAuth changes, so I didn't do any testing but rewrote authentication routine in the app to use OAuth because I knew that I needed to do it eventually anyway. Sorry

I can't be of more help. Anyway, if it's working for you then no need to waste any more of your time on it. Thanks for checking.

* but rewrote the authentication routine

I use a beets plugin that just takes username and password and it's still working for collection stuff. Unless it's also doing oauth in the background.

I'm guessing it isn't doing the OAuth stuff. Must just have been something unusual with my system.

<BobSwift[m]> "I haven't checked using curl..." <- no problem, that's odd that it broke so suddenly. the curl command I was using is just `curl --digest -u user:pass -X PUT ...` if you'd like to try again in the future

[musicbrainz-server] 14reosarevok merged pull request #3396 (03master…remove-useless-ws-opts): Remove useless API definitions https://github.com/metabrainz/musicbrainz-serve...

Hi, sorry, couldn't make it for the meeting and forgot to mail in 🙄