Frequently asked questions
Questions about scrobbling, trackers and portable records.
Start with the practical difference. Follow the project link when an answer depends on current behaviour.
Why is anime a separate catalogue facet?
Anime is a separate filter because it helps people find projects that track episodes, specials, split releases, continuing titles and rewatches. It is a navigation choice, not a claim that anime sits outside film or television.
A project can appear under anime and another media type. The facet should remain only while it helps people find relevant tools and tracking behaviour.
How do common tracking projects differ?
Projects differ in media scope, capture method, hosting model and the records they keep. Some receive playback events, some provide a diary, some keep listening history, and some store a self-hosted record across several media.
Swipe the table sideways to compare every column.
| Project | Main scope | Typical record | Useful when |
|---|---|---|---|
| Floppy | Ten media types | Library, history and progress | A self-hosted, cross-media record is required. |
| Last.fm | Music | Submitted listens | Players and services submit listening activity. |
| ListenBrainz | Music | Open listening history | An open-source service and exportable listening data are required. |
| Trakt | Film and television | History, progress and playback events | Media applications report playback activity. |
| Simkl | Film, television and anime | History, lists and episode state | One service covers its three advertised media areas. |
| Letterboxd | Film | Dated diary entry, rating, review or list | The task is film logging rather than live playback progress. |
| WeTrakr | Film and television | Kodi playback events | Kodi playback is sent to a tracking service. |
The project catalogue records source availability, licences and contribution routes. It describes projects; it does not rank them.
What should a portable scrobble preserve?
A portable record should preserve enough information to identify, interpret, retry and correct the event:
- A stable event identifier.
- The media type and the source-local identity known when the event was recorded.
- The event time and, when different, the recorded time.
- Progress in the medium's native unit before a percentage is derived.
- Provenance, including whether the record came from playback, manual entry, import or synchronization.
- Correction or deletion state and enough retry information to prevent duplicate history.
These fields do not guarantee that two systems will make the same decision. They preserve enough context to explain a difference and correct the resulting history.
Can the Scrobble.dev catalogue be reused commercially?
Yes. Scrobble.dev releases its project catalogue under CC0, which permits copying, modification and commercial reuse without asking Scrobble.dev for permission.
That dedication covers the catalogue published by Scrobble.dev. Linked projects, repositories and upstream data retain their own terms. A software licence does not automatically grant rights to data used by that software. The European Commission's database-protection summary explains the separate rights that may apply in the European Union. This is an editorial summary, not legal advice.
How can I contribute?
For a factual correction or project update, open a Scrobble.dev issue. Include the claim, a primary source and the date checked. The editorial method explains how claims and draft proposals are labelled.
For application changes, use the Floppy issue tracker or the FloppyDesktop issue tracker. Include the media type, event sequence, observed result, expected result and a private-data-safe example.