Intersect.Ninja was an open source website that uses the Spotify Web API to find intersections in the artists and tracks different people like, based on their public playlists.
How does Intersect.Ninja work?
When users visits Intersect.Ninja, they’re prompted to connect with their Spotify account, which starts the server-side authentication flow.
After authenticating, Intersect.Ninja saves the temporary access key it received from Spotify in HTML5 local storage; everything else happens client-side. From a privacy point of view, this is great since none of your data ever leaves your device.
As other users are added through the form at the top of the page, Intersect.Ninja retrieves their public playlists and crunches them to keep track of which users like which artists and tracks. It’s also possible to click on a user to exclude some of their playlists from the matching process.
This data is displayed below the list of users, in the form of a table of artists’ names, sorted first by how many users have tracks by that artist in their public playlists, then by how many tracks by the artist these users have, and then alphabetically by artist name.
Clicking an artist reveals a table that contains the tracks by that artist that are in users’ public playlists, and which users like each track. The table is sorted first by how many users like the track, and then alphabetically by the track’s title.
That’s the basic gist of the website. In the future, I’d like to add some more functionality, such as the ability to make a playlist of tracks from intersecting artists from within the interface.
Tech Stack and Source Code
Intersect.Ninja is the first project I’ve made that’s completely open source, and it’s licensed under the MIT License. You can check out the source code on GitHub.
There’s some pretty cool stuff in there, like the sorting algorithms that are easily chainable for tie breaking, and also some stuff that could use improvement, like the way enabling / disabling some of a user’s playlist is implemented.