A daily new-music feed
Every morning the build reads Last.fm, ListenBrainz, MusicBrainz, Bandcamp, Deezer, radio playlists and a few dozen blogs, scores what it finds against one listener's taste, and lists the best of it here. Press play on any card, or space, and it plays on through the list.
Sign in with Google and the Keep / Skip buttons appear: Keep files a track into a year playlist in your own YouTube library, Skip hides it for good. Install the site as an app for a full-screen deck with lock-screen controls.
Cleanup
How this works
The daily build reads every year playlist and lists each song it holds more than once — the same video twice, the same song in two years, two uploads of it (the audio track and the video, say), or two editions of it (the original and a remix, the radio edit and the extended mix). Every copy is laid out with its edition, length, album, position and whether it plays here; ▶ plays a copy in place so two can be heard back to back, and look up the copies asks YouTube what each upload is (1 unit per 50). Choose a copy with its radio button and keep the chosen copy removes the rest; ✕ removes one; move to… refiles a copy into another year (the verified year is marked ✓, and a song filed entirely in the wrong year gets a one-tap move everything); looks fine · dismiss keeps every copy and stops listing the song. A removal costs 51 YouTube API units, a move 102. What you do here is remembered on every device you sign into, and the next build drops what is gone.
Not streamable here lists the tracks that will not play in the US: what the build's scan found greyed out on YouTube Music, plus what the playability audit below finds — deleted, private and region-blocked videos, which YouTube Music's listing hides altogether. The build searches for a playable upload of each (free, overnight) and a swap adds it and removes the dead copy; find a replacement now does the search from here for 100 units.
Scan a year now
The report above is from the last build; a live scan reads one playlist as it is right now (1 unit per 50 tracks), groups it by song the same way, and catches today's double-taps and second uploads before the nightly build does. Removals here need no lookup: the scan already knows each row.
Playability audit
Which tracks cannot play in the US at all: the playlist is read through the YouTube Data API and every video is checked with YouTube (about 2 units per 50 tracks) — a video YouTube no longer answers for is deleted or private, one restricted away from the US is blocked. Findings go under not streamable here above, are kept on this device, and travel to the build with your ratings so it can look for a playable upload of each overnight.
Video
How this works
The year playlists hold audio tracks; YouTube Music pairs most of them with an official video. This tab is the one place videos are reviewed. Two things put a video here: a song you keep on the Feed or the Catalog whose card knows its video side (the daily build asks YouTube Music for it as it resolves each card, so the video is here the moment the song is kept), and every song in every year playlist that has a video — the Videos workflow asks YouTube Music about the library a batch a day (free) until every row has been asked, then keeps up with what is filed. One video is one row, however many years hold the song.
The cards work like the Feed's: ▶ (or space) plays the video in the player, and with autoplay on the list plays on down; j/k move, u and d decide, z undoes, a swipe right or left decides on a phone, and the player's own thumbs judge what is playing. ▲︎ puts the video into the music-video playlist — the single playlist every approved video goes to, and the only thing this tab ever writes (50 units, plus 1 to verify it is not already there unless the playlist was read in the last half hour); ▼︎ passes for free and is remembered. Decisions travel with your ratings to every device and to the daily build, which leaves them out of the next list; read the playlist hides what it already holds, from another device or from YouTube Music itself.
Concerts near Detroit
How this works
Every afternoon the Concerts workflow takes every artist played on Indie Discotheque in the last year — the Last.fm 12-month chart of tt_discotheque, plus anyone filed into this year's playlist — asks Bandsintown where each of them plays next (a batch a day, so the list fills in over its first few runs), reads every listing in the radius from Resident Advisor, Ticketmaster, SeatGeek, Edmtrain and JamBase (each where its key is set; JamBase's six months in date bands, the near future refreshed often, held under its monthly quota), keeps what is within 80 miles of Detroit, and looks up each act's most popular song on Last.fm (Deezer without a key) and on YouTube Music, so ▶ plays it right here. The ticket button names the seller where the link says so (Ticketmaster, TicketWeb, AXS, Etix, DICE…) and shows the price where Ticketmaster or JamBase lists one (SeatGeek's is its lowest listing; Bandsintown and RA publish none); a Bandsintown, JamBase or Edmtrain link leads on to whichever seller the venue uses. A show several of them list is one row with every link, and the line under the summary credits each listing the rows came from. Search matches artists, venues, cities and song titles; space plays the first song on the list, j/k walk down it, and an artist's name opens their sheet.