About Scrobble.dev
A maintained reference for scrobbling and media activity.
Scrobble.dev explains how media activity becomes progress and history, documents implementation choices, and compares projects without declaring a winner.
What the site covers
Scrobble.dev covers activity, now playing, progress, completion, durable history, retries, correction, deletion, synchronization, portability, privacy and project capabilities. It treats Fasti as an implementation that can exercise these ideas, not as the definition of scrobbling.
The site does not rank projects or require another project to depend on Scrobble.dev at runtime.
How claims are described
Each claim should make its basis clear. Project documentation is attributed to the project. Reproduced behaviour identifies the version and method. Historical material is labelled historical. Editorial conclusions are labelled as interpretation. Scrobble.dev proposals name their draft and version.
| Claim class | Meaning | Expected wording |
|---|---|---|
| Official requirement | An upstream specification or API states a requirement. | “The API requires…” |
| Project statement | A project's current documentation states a capability. | “The project documentation states…” |
| Observed behaviour | A result was reproduced against a named version. | “A test against version X produced…” |
| Historical record | An archived or retired source describes earlier behaviour. | “Historically…” |
| Interpretation | The conclusion follows from cited evidence. | “This suggests…” |
| Proposal | A versioned Scrobble.dev draft recommends behaviour. | “The draft profile proposes…” |
| Unknown | No adequate source was verified. | “Not verified as of DATE.” |
The full method is available as plain Markdown.
How current facts are checked
Current project facts should include a primary source and a verification date. A stale date triggers review; it does not silently turn a fact into false. Where documentation does not establish a capability, the catalogue records that the claim is unknown or not verified.
Descriptions state what a source establishes and avoid inferring capability from a logo, dependency, issue title or marketing phrase.
How changes are governed
Factual corrections can use a focused issue or pull request. A material definition change needs its motivation, evidence and compatibility effect. A draft-profile change needs an example or conformance case and must state whether it clarifies, extends or breaks the previous version.
Open questions may remain open. Finishing a page is not a reason to invent consensus. The governance note records the review path.
Technology & Design System Credits
Scrobble.dev is built with static-first, lightweight open standards:
- Tabler Core: High-quality, accessible UI component kit and design system licensed under MIT by Paweł Kuna.
- Astro: High-performance static site generator with zero JavaScript overhead by default.
- Open Knowledge Format (OKF v0.2): Machine-readable knowledge catalogs for media and data definitions.
- Slashfriends: Decentralized blogroll and peer discovery federation protocol.
Who maintains the work
The public Scrobble.dev repository records contributions and review history. Project facts can be corrected through its issue tracker.
Application work belongs in the Fasti issue tracker. Those contribution routes remain separate from editorial corrections.
Scrobble.dev maintenance can be supported through Ryan's GitHub Sponsors page.