Right now, I have my Last.fm scrobbles backed up. Every day, a small script fetches everything from Last.fm and dumps it into a file. The script is not very well optimized and downloads every scrobble since ever every day. Anyways, the point is not that. I would love to have the things I listen to in this website, just like I have for the watches. But there’s a problem: the sheer amount of data!

Since mid-2020 until right now, I have 32 526 scrobbles on Last.fm. Doing the math, I have, on average, a little bit more than 50 scrobbles a day. That would be 32K posts. That would generate too many posts, at least in my opinion. I’m sure Eagle, and of course Postgres, would be able to handle it. However, it would easily pollute my omni feed. One of my ideas was to put all the daily scrobbles in a single file that would be rendered as multiple entries. Basically, every time my Micropub endpoint would receive a scrobble, it would append it to the the publishing day’s scrobble file. I will sleep on this idea.

I know that some people, like Jamie, do a yearly music review post. Do you have any other examples?

Right now, I have my Last.fm scrobbles backed up. Every day, a small script fetches everything from Last.fm and dumps it into a file. The script is not very well optimized and downloads every scrobble since ever every day. Anyways, the point is not that. I would love to have the things I listen to i…

Interactions (1)
Henrique Dias Henrique Dias said: A few days ago I mentioned that I wanted to ditch my daily Last.fm backup script and instead publish the scrobbles on my website. Well, I did it! Instead of publishing a post per scrobble, I automatically create a post that contains all the scrobbles from that day (yesterday example). In addition, e…28 Mar 2022 22:37