Rocksky
To monitor and re-scrobble activity from Rocksky create a Rocksky (Source)
Rocksky is music tracking and discovery platform built on the AT Protocol (Bluesky).
How does that work?
The AT Protocol is a standard to allow different applications to share and interpret your social data.
Your data is stored in a personal repository in a PDS (Personal Data Server), which is data-type agnostic (it's just JSON). Each application defines their own datatypes and pulls data from your repository to render to you, your network, etc...
Even though the application and the PDS/repository are independent, all of this is done for you automatically when you create a Bluesky account.
So...
- multi-scrobbler "scrobbles" your plays to your repository
- in a JSON data structure which includes Rocksky's data type and structure
- at a known location for Rocksky's data (
app.rocksky), in a list that is appended to as you continue to scrobble
- when accessing Rocksky, or another application that knows how to read it, your data is pulled from the repository to render the app
The default Bluesky PDS is public, meaning your scrobbles are also public (read-only). This isn't any different than using Last.fm or Listenbrainz, in terms of privacy.
Rocksky does not guarantee that every scrobble you send will be persisted. Rocksky's design goal is to store scrobbles with metdata-complete, 3rd party verifiable track information so that it can be a metadata-rich discovery platform, rather than an exhaustive scrobble data source-of-truth.
To do this it asynchronously matches your scrobble data against Musicbrainz's and/or Spotify's catalogs, after the scrobble has been submitted. If the scrobble does not end up matching then it is not persisted.
If you need your scrobbles to be 100% captured then you should scrobble to an additional Scrobble Client.
Setup
You will need a Bluesky account to use Rocksky.
Usage is adapted from Rocksky docs on docs.rocksky.app
- Navigate to rocksky.app and sign up/logn using your Bluesky account
- Then, navigate to the RockSky developer dashboard and obtain an API Key
Configuration
Handle
The handle used with multi-scrobbler should be your full ATProto handle, including TLD.
- For regular Bluesky account this will be like:
alice.bsky.social - For Bluesky accounts that use their website as their account this is your domain:
mydomain.com - For non-Bluesky users, you probably already know your handle
If you do not include a TLD then multi-scrobbler will automatically append .bsky.social to your handle value.
- ENV
- File
- AIO
| Environmental Variable | Required? | Default | Description |
|---|---|---|---|
| ROCKSKY_HANDLE | Yes | Your full ATProto handle. For Bluesky account this is like myUser.bsky.social | |
| ROCKSKY_KEY | Yes | API Key obtained from Rocksky developer dashboard |
[
{
"name": "myRockskyClient",
"configureAs": "client",
"data": {
"key": "7cdr86vis3mpq5b1pi01md0hkm7ykzzxjy81r",
"handle": "alice.bsky.social"
}
}
]
or explore the schema with an example and live editor/validator
{
"clients": [
{
"name": "myRockskyClient",
"configureAs": "client",
"data": {
"key": "7cdr86vis3mpq5b1pi01md0hkm7ykzzxjy81r",
"handle": "alice.bsky.social"
},
"type": "rocksky"
}
]
}
or explore the schema with an example and live editor/validator