Teal.fm
To monitor and re-scrobble activity from a ATProto Profile create a teal.fm (Source)
teal.fm is a social discovery and web viewing service for scrobbles stored/available on the ATProto network/your repository in a PDS (Personal Data Server).
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 teal.fm's data type and structure
- at a known location for teal.fm's data (
fm.teal), in a list that is appended to as you continue to scrobble
- when accessing teal.fm, or another application that knows how to read it, your data is pulled from the repository to render the app
Your Data Is Public
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.
teal.fm Is Still In Development
teal.fm is still in developement and does not have a true production website, yet.
To view your teal.fm scrobble data you can:
- use teal-relay-production.up.railway.app or teal-slice.wisp.place for a preview of teal.fm
- use yearinmusic.teal.fm or wrapped.baileytownsend.dev for wrapped-style stats of your teal.fm scrobbles
- use atproto.at to view the raw data (convenience URLs are generated in multi-scrobbler, per scrobble, for you to do this)
Setup
Bluesky
- Create a Bluesky account, if you don't already have one
- Navigate to https://bsky.app/settings/app-passwords
- Settings -> Privacy and Security -> App passwords
- Create a new App Password and save it somewhere, it will not be shown again
Configuration
Identifier
The ATPRoto identifier used with multi-scrobbler should be either:
- A valid DID, starting with
did:plc:...ordid:web:... - Your full ATProto handle, including TLD
If using a handle:
- For regular Bluesky account this will be like:
alice.bsky.social - For Bluesky accounts that use their domain as their account this is your domain:
mydomain.com - For non-Bluesky-PDS users, you probably already know your handle
If your identifier does not look like a DID and does not include a TLD then multi-scrobbler will automatically append .bsky.social to your handle value.
- ENV
- File
- AIO
This is configuration for the ENV Config Type.
| Environmental Variable | Required? | Default | Description |
|---|---|---|---|
TEALFM_IDENTIFIER | Yes | Your full ATProto handle or DID. For Bluesky account this is like myUser.bsky.social | |
TEALFM_APP_PW | Yes | Bluesky/ATProto network App Password |
Config Structure
This displays the structure of the File Configuration for a tealfm type Client with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.
Config Example
This displays an example config file of a tealfm Client File Configuration that adheres to the shown Config Structure.
- text mode lets you edit the JSON directly.
- tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.
Both modes validate that the configuraion is correct. Any errors show up as squiggly lines.
After you finish editing, switch to text and then copy all text to get a completed config.
Config Example Mobile Experience
This displays an example config file of a tealfm Client File Configuration that adheres to the shown Config Structure.
The example config file editor is meant for a larger screen experience so only the read-only example is shown. Please use this site on a tablet/laptop/desktop to enable file editor features.
[
{
"name": "myTeal",
"configureAs": "client",
"data": {
"identifier": "alice.bsky.social",
"appPassword": "twog-phu7-4dhe-y4j3"
}
}
]
Config Structure
This displays the structure of the all-in-one (config.json) configuration with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.
Select the tealfm type from the respective clients node below, then expand it.
Config Example
This displays an example config file of a all-in-one (config.json) configuration that includes a tealfm Client that adheres to the shown Config Structure.
- text mode lets you edit the JSON directly.
- tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.
Both modes validate that the configuraion is correct. Any errors show up as squiggly lines.
After you finish editing, switch to text and then copy all text to get a completed config.
Config Example Mobile Experience
This displays an example config file of a all-in-one (config.json) configuration that includes a tealfm Client that adheres to the shown Config Structure.
The example config file editor is meant for a larger screen experience so only the read-only example is shown. Please use this site on a tablet/laptop/desktop to enable file editor features.
{
"clients": [
{
"name": "myTeal",
"configureAs": "client",
"data": {
"identifier": "alice.bsky.social",
"appPassword": "twog-phu7-4dhe-y4j3"
},
"type": "tealfm"
}
]
}