scrobbling is the act of passively publishing scrobbles.
The term "scrobble" comes from Last.fm's software, Audioscrobbler.
- Musicbrainz ID. Each of the data elements has a p-* with the Musicbrainz ID of the various Tracks and Albums where it's available.
- Album images.
It annoyed me that Last.fm served images without HTTPS, so I cached the imagery for every track. I need to run a checksum comparison of images to remove duplicate files at some point.
tommorris publishes links to DJ sets (mostly from Mixcloud) and some songs (mostly from Spotify) manually (and actively rather than passively) and tags them currently playing. May start PESOS-ing from Mixcloud or using a bookmarklet.
He also displays all of his tracked listens on his website at http://davidpea.ch/listens
Libre.fm and GNU FM
WordPress Audioscrobbler server
The WordPress Audioscrobbler plugin can receive and store v1.2 scrobble requests as custom post type.
Creating an IndieWeb implementation of a scrobbling server or pass-through relay would free data about one's music listening activity and history from the Last.fm silo. One would scrobble tracks to their own personal server before syndicating the activity to other social sites like Last.fm. All of the scrobbling activity would be archived in a database on one's personal web server. A simple implementation need only implement the basic functionality present in the Last.fm API such that existing Last.fm client software could be used with minimal modification.
Ideas for advanced features
Scrobbling activity could be syndicated in other formats (i.e. Activity Streams), or published in another form altogether such as a tweet or status update.
Scrobbling activity could be filtered prior to syndication. For example, before publishing a track, the software could first check the artist and/or track name is not present in a list of "guilty pleasures."