# Scrobble.dev: expanded context

Canonical site: https://scrobble.dev/
Repository: https://github.com/Scrobble-dev/scrobble.dev
Language: en
Last revised: 2026-08-31

Scrobble.dev is a maintained field guide to scrobbling, portable media history and tracker interoperability. Draft profiles carry their own status and version; the site as a whole is not an adopted industry standard.

## Definition

A scrobble is a durable record of what someone watched, read, heard or played, and when. It may also preserve native progress, completion state and provenance.

The player can say what is happening now. Progress says where to resume. A scrobble says what happened and when. Completion says whether a chosen unit counts as finished. Synchronization moves or reconciles those records. Keeping them separate makes retries and corrections explainable.

## Evidence method

Scrobble.dev distinguishes official requirements, current project statements, historical records, observed behaviour, editorial inference, draft proposals and unknown facts. Current project claims should identify a primary source and the date checked. Unknown is not treated as false.

- Editorial method: https://scrobble.dev/about/
- Portable method file: https://scrobble.dev/knowledge/method.md
- Governance: https://scrobble.dev/knowledge/governance.md

## Portable event core

1. Stable event identity makes an ordinary retry harmless.
2. Source-local media identity preserves what the sender knew about the subject.
3. Named timestamps distinguish event time from recorded or received time.
4. Native progress retains seconds, pages, chapters, sessions or turns before deriving a percentage.
5. Provenance distinguishes playback, manual entry, import, inference and synchronized copies.
6. Correction and deletion allow a person to repair misidentified or duplicated history.
7. A documented export allows a person to inspect and move their history.

## Medium-specific activity

Music projects commonly separate capture clients from independent listening-history destinations. Podcast projects more often synchronize subscriptions, playback position and completion among compatible clients. Those records should not be treated as identical without project evidence.

Game activity can be an observed session, cumulative playtime, a platform snapshot, an achievement event or manual state. A portable record keeps the capture source and does not infer session history from one total.

Anime services can divide the same material into different entries, parts, specials and season structures. An import should retain the source entry and episode coordinates, keep missing watch times unknown and permit an unresolved subject rather than forcing an unsafe destination entry.

- Audio and podcast guide: https://scrobble.dev/learn/audio-and-podcasts/
- Game activity guide: https://scrobble.dev/learn/games/
- Anime catalogue-granularity guide: https://scrobble.dev/learn/anime-catalogues/

## Project directory

The project catalogue describes services, trackers, clients and connectors by media, category, capture method, source state, checked date and contribution route. Inclusion is not an endorsement, and the catalogue does not rank projects.

- HTML: https://scrobble.dev/projects/
- JSON: https://scrobble.dev/projects.json
- CSV: https://scrobble.dev/projects.csv
- OKF v0.2 Markdown: https://scrobble.dev/knowledge/projects.md
- OKF project: https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf
- Pinned OKF v0.2 specification: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/374e0bc4c644310ff56cdf9c0fe81eccdec862b0/okf/SPEC.md

Scrobble.dev releases its catalogue under CC0. Linked projects, repositories and upstream data retain their own terms.

## Frequently asked questions

The FAQ explains the anime catalogue facet, differences between common trackers, the minimum context a portable record should preserve, catalogue licensing and contribution routes.

- FAQ: https://scrobble.dev/faq/
- Portable FAQ file: https://scrobble.dev/knowledge/faq.md

## Contribution

Scrobble.dev accepts factual corrections, project updates and documented tracking edge cases. Contributions should identify the claim, a primary source and the date checked.

- Scrobble.dev: https://github.com/Scrobble-dev/scrobble.dev
- Fasti issues: https://github.com/Scrobble-dev/Fasti/issues

Do not infer consensus, compatibility or current project capability from an uncited summary. Prefer the cited project documentation, repository or protocol.