#listenbrainz

hello, is there an API endpoint for taste section?

weekly playlists also gets automatically exported to Spotify now, huh

Done. It's in the new version

also these are not automatically deleted it seems

Thank you very much, now I just need to get Listenbrainz and Musicbrainz up and running

Does someone know how to use the Dockerifle.nginx.prod file? I'm not sure how WSGI works and don't know where to deploy it

There's no way to set the MusicBrainz URL yet. I'm stuck dealing with rust not liking me passing down sql executors and reusing them.

*Screaming in crab*

/1/feedback/recording_feedback

It's under "recording" in the api docs

cmd

Whoops

Oh- Looks like MB returned something that isn't in the api schema. What's your lb username again? I'll try to find it on my side

<rustynova[m]> "Oh- Looks like MB returned..." <- https://listenbrainz.org/user/egecelikci/

but I just deleted bunch of listens so it could be one of them

I know that it broke when fetching a parent work. So I think it may be an instrument or work relation that isn't set in the schema.

I hope I catch it because that it's actually a pain to find those

<ruebeckscube> "hi folks! new here, super..." <- Hi! Sadly restricting the DB isn't possible right now. You might consider using the API to fetch the data you need -- that depends on how much data you really need to fetch.

<rustynova[m]> "I know that it broke when..." <- might be this one?

* this one: https://musicbrainz.org/recording/7afa92fe-3f8f... ?

Well I can't check right now, but I'll see after lunch

<hash[m]> "hello, is there an API endpoint..." <- https://listenbrainz.readthedocs.io/en/latest/u... is where those endpoints are documented.

<mayhem[m]> "https://listenbrainz.readthedocs..." <- pins?

pins what?

I was asking. I couldn't find anything related to taste in the docs you linked

feedback = love/hate, pins = pins. not sure what else to tell you.

oh alright. thanks

I did a sample of a year of listens and i'm still not past the recording fetching phase.

Would love to improve the speed of the recording redirect fetching, but when it comes to works, I'd get like 1% of speed Improvement

Or I could try adding a multi mirror fetcher to parallel the fetching

<mayhem[m]> "Hi! Sadly restricting the DB isn..." <- the similar-artists API is def an option, but I would love to be able to access the raw similarity scores for two mbids that are stored in the database—considered trying to contribute an API for that but I'd be calling it like 1000 times for each search on my website so not really feasible even in a batched setup

i think I might just have to suck it up and pay for more server storage! the docs mention building indices locally, I'll see if I can limit that to the ones I need to save space