Contribute
Contribute to the guide or the software.
Bring evidence to the guide. Bring a reproducible failure to Fasti. The first changes what people know; the second changes what software does.
Two ways in
Knowledge on one side. Software on the other.
Scrobble.dev
Add or correct knowledge
Bring a first-party source, a factual summary and one missing or incorrect claim. Project catalogue entries must name the media type, role, capture method, source availability and contribution route.
- Use plain Markdown and stable links.
- Keep one topic or correction per change.
- Separate documented behaviour from interpretation.
Fasti
Fix a tracking failure
Name the media identity, the observed event, what the software recorded and what should survive a retry, correction, import or export.
- Add an anonymized example or reproducible sequence.
- Name provider identifiers and numbering schemes.
- Include a round-trip test when code changes behaviour.
A useful issue
Make the problem reconstructable.
- Context
- Media type, player, tracker, integration direction and relevant versions.
- Identity
- Provider IDs and titles, with personal account identifiers removed.
- Observed
- The event or state that actually occurred.
- Expected
- The event or state that should have resulted and why.
- Round trip
- What happens after export, repeat synchronization, correction and import.
- Evidence
- Logs, API payloads, fixtures, screenshots or documentation sufficient to verify the claim.
Knowledge contributions also update the Open Knowledge Format v0.2 bundle when a reusable concept changes.