Contribute

Contribute to the guide or the software.

Bring evidence to the guide. Bring a reproducible failure to Floppy. 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.

Suggest a site change Edit the repository

Floppy

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.

Browse Floppy issues Read the contribution guide

A useful issue

Make the problem reconstructable.

ContextMedia type, player, tracker, integration direction and relevant versions.

IdentityProvider IDs and titles, with personal account identifiers removed.

ObservedThe event or state that actually occurred.

ExpectedThe event or state that should have resulted and why.

Round tripWhat happens after export, repeat synchronization, correction and import.

EvidenceLogs, 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.