#listenbrainz

letoseldon: welcome ! Sad and enraging to read all those comments on the Spotify forums of frustrated developers that got rug pulled 😡

Your recommendations playlists will be better if you can get your hands on your spotify extended streaming history and import it.

At the moment that process is a bit involved: you need to request your history from spotify, wait a few weeks, download the files, then use a third-party CLI tool like Elbisaur to import those files.

The spotify history request is on the page https://www.spotify.com/es/account/privacy , and for the import tool: https://github.com/kellnerd/elbisaur/blob/main/...

Does the daily playlist refresh every morning in the users timezone monkey ? Do we have an approx time or is it variable enough that we just say “morning” (I’m assuming that’s the reason…)

I looked at the code for it, looks like it is run everyday at midnight (I'm assuming midnight UTC or CET)

So, yeah, should refresh every day, but its a relative "morning"

<letoseldon[m]> "Ha, very good to know! Thank you..." <- > <@_discord_492889197926154250:chatbrainz.org> Ha, very good to know! Thank you. It's helpful to know that the description of the weekly playlist states that it updates on Monday morning. That being said, as a new user, I don't get to see these descriptions on... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

*this week, not yesterday

I still think we need a better page that this documentation page, or we need to review it and make it more user-friendly

That makes me think. Do people like their weekly jams? Personally I don't listen to them as they are full of recordings I only listened to once and never again. (And I got alistral for my daily 10 hours work playlists)

As for exploration playlist, I prefer Spotify's as it fills my missing data page, giving me more stuff to add~

some people really like them, others are meh. you on the other hand are a metadata geek

They are Listenbrainz user, I'm a MusicBrainz user. We are not the same.

exactly. needs the meme image now. :)

But still curious. Since it should be ready for the onslaught of angry Spotify nerds

not sure that will happen. it would've happened already

~~ we'll see. I am also of the opinion that recommendations can be improved. The main vector of improvement would be more LB users, so it's a waiting game

+ improvements to our recs system, which also require a lot of work and are hard to evaluate

Definitely need more LB users, at least in the dubstep space. There's plenty of similar artists that are not the best matches, and I keep having recommendations of artists I don't like because my similar users listen to them.

There should probably have a bit more "artist you listened to recently" in there as well.

I don't have any above 13 compatibility tho, apart from one at 16 but with so little listens that the stats is thrown off

Thanks for your help. I requested my extended history and set up `elbisaur`. It's a nice tool. Glad I finally get to use something written with Deno. 🙂

I noticed that `https://listenbrainz.org/recommended/tracks/:user_name` has started populating with track recommendations today. Is there a way to get the Spotify ID of these recommended tracks? I started playing with the ListenBrainz API and `/1/metadata/recording/` doesn't seem to give much metadata on the recordings from my listening history.

* I noticed that `https://listenbrainz.org/recommended/tracks/:user_name` has started populating with track recommendations today. Is there a way to get the Spotify ID of these recommended tracks? I started playing with the ListenBrainz API and `/1/metadata/recording/` doesn't seem to give much metadata on the queried recordings.

Maybe I should be querying the MusicBrainz API?

LB has this functionality internally for its "play on Spotify" feature, but I'm not sure if it's exposed as an API somewhere

The Musicbrainz API can give you Spotify URLs for releases and potentially recordings, but the latter is quite rare

(also note that since this channel is bridged to IRC, people might not see what you are replying to when you use the Discord reply feature)

elomatreb[m]: Not really, I'm afraid. If the spotify ID is part of the listen data sent by a user (i.e. not on recommendation playlists we create) we use it, otherwise we just use the Spotify search API

letoseldon: However once you do get a recommendation playlist, you can export it to Spotify.

Never mind, I spoke too soon!

If you have a recording MBID: https://labs.api.listenbrainz.org/spotify-id-fr...

If you don't have one: https://labs.api.listenbrainz.org/spotify-id-fr...

To get the recording MBID, either: copy the link of the listen track title OR got the the '...' menu on the right and click on "inspect listen", look for "recording_mbid"

P.S: these labs.api.listenbrainz endpoints can be called programatically and be sent a JSON object. Just add "/json" to the end of either of those endpoints

Oooooooh! That's so great! Exactly what I need!

Thank you!

If you do try to Export to Spotify you may need to copy the playlist to your profile then remove the description to get the export to work

The Weekly Exploration's description is too long and makes the export error

Actually, it looks like the descriptions on all of them are too long except the Daily Jams playlist

Good to know! Thank you.

Thought this was funny

Oh right! I forgot I needed to add a "today in history" feature.

monkey: I’m going to do a PR for the docs this weekend so I want to clarify, daily playlists run at global midnight? Not based on user settings? Weekly ones generate based on user settings/when that user’s Monday morning is

Though I assume a PR will be seen and fixed by mayhem, I’m guessing, who I should have probably asked in the first place. I forgot that those playlists are his bebe

If you're looking at adding when the playlist generates to the description for the daily playlists, maybe add it outside of the annotation? Since that's what's breaking Spotify imports for all the other playlists. Or make a disclaimer that you have to delete the annotation to actually import it to Spotify

Of course the optimal solution is to just truncate the annotation when it's sent to Spotify, but if you're just editing the annotation text in the meantime

Well, I was able to replace the deprecated Spotify recommendation endpoint with a solution that uses ListenBrainz. Thank you all for your help! I'm looking forward to seeing the recommendations getting refined as I continue to listen to music. 🙂

* recommendation endpoint in my app with a