House rule
| Album | Genre | Open |
|---|
Nothing matches that.
Each playlist is a fixed set, so a search only finds what is already in it. Press Esc to clear, or switch playlist with [ and ].
Add a song
Every playlist is a JSON file in the open. Adding a song means adding one line to it and opening a pull request; proposing a whole playlist means adding one file. There is no account to make and no gatekeeper to convince — the review is about whether the entry is accurate, not whether the taste is correct.
Two rules do most of the work. One song per artist per playlist, so no single act can dominate a list. And a note that says something true and non-obvious about the recording — an arrangement detail, a production fact, a piece of history. Not a review.
Every pull request is checked automatically: contiguous numbering, no repeated artist, genres drawn from the shared vocabulary, real punctuation, and three valid platform links per entry. If the check passes and the facts hold up, it gets merged.
How the links work
Each entry carries facts — title, artist, album, year — and nothing else. The three platform links are built at render time from the artist and title using each service’s own search endpoint.
That is deliberate. Hard-coding track IDs would mean writing IDs that were never verified against the real APIs, and a wrong ID sends you to the wrong song silently. A search link is always correct, survives regional catalogue differences, and keeps working when a track is re-released.
Verified IDs are still welcome. Any entry that carries one deep-links straight to the track instead of searching for it — the renderer prefers an ID whenever it finds one.