Owning my music data

At Homebrew Website Club on Wednesday, GWG challenged me to explore owning my scrobbles, pointing me to Jan’s implementation (GitHub). I said I listen to way too much music and I’d need to do a separate WordPress install on a subdomain dedicated to tracking listens, so I ruled it out.

Except then I came across ClassicPress and am curious about trying it out.

And I decided to port my playlists from Spotify to Tidal and got correspondingly irritated about walled gardens and data portability and losing the full record of some of my playlists because Tidal doesn’t have rights to some of the songs. And I came across kandr3s’ online playlists where his playlists are recreated in order with links / embeds to play the songs.

So now I’m thinking about it 😂 #idontneedanotherwebsite

Not making any promises…but pondering what my goal would be with the data. Would it be just a backup of that I owned, or would I be able to manipulate the data more than I could there?

Keeping accessible format playlists has some appeal, although potentially a lot of manual work unless I found some way to transform the csv files I downloaded from Exportify into a blog post. The files do include the Spotify URIs for the tracks, albums and artists so I’m sure there’s a way that I’d just have to figure out. Although, I’d want to give more thought to what I would use the playlist for, to make it a useful format.

I feel like there should be a micropub client for listens, really, where you had (later searchable and sortable) fields for track, artist, album, and year the album came out. Something like indiebookclub, except indiemusicclub 😎

Actually, this type of listening library is another type of personal library for me to get ideas about at the upcoming Personal Libraries Pop-Up.