I collect records and I build apps in my spare time (and listen to records while I build apps), and this is what happens when those two things run into each other.
Many people post photos of what they have spinning on their turntables on social media, and most never get any engagement. It occurred to me that people might want a better way to do this, and bringing them together in a niche social site might help.
So I made Wax Spinner. Connect your Discogs (the de-facto vinyl collector's catalogue) account, post whatever you're playing with an optional note, and it lands in a feed where people can like it and comment. You can also browse anyone's full collection on their profile, and filter the feed by genre, pulled straight from Discogs metadata.
The conversation and the discovery are the primary purpose.
The details this crowd might find interesting: every spin generates its own OpenGraph share card on the fly, with cover art, artist, year, and notes rendered server-side and cached. Getting it to actually display everywhere took way longer than building it. next/og (Satori) only outputs PNG, and the ~800KB it produced was silently dropped by some crawlers' image-fetch limits, so I re-encode to a ~95KB JPEG with sharp. Slack was the biggest hurdle, and as it turned out, my global security headers (X-Frame-Options, CSP) were attached to the image route too, and Slack's proxy refuses to embed anything that signals it can't be framed. Also had to serve the image from a clean static-looking path instead of a query-stringed API route, because Slack's fetcher is oddly picky about URL shape. It now unfurls properly on Discord, iMessage, Facebook, Bluesky, and Slack.
The stack is Next.js (App Router) on Vercel, Supabase for Postgres and auth, Discogs API for collection data.
Known limitation: collection import uses an app-level Discogs token, so it only pulls public collections, no per-user OAuth yet.
It's free, no ads, not selling anyone's data. Side project, not a startup, so I'd rather have honest feedback than signups. It's brand new and quiet right now, and a social site is nothing without people in it, so I'd love to hear what's confusing, what's missing, or what would get you to actually open something like this on a Sunday afternoon when you put a record on.
I don't code full-time anymore, but I used to build dating websites in the early 2000's (php, mysql). I used Claude Code to build this as a side project.
Many people post photos of what they have spinning on their turntables on social media, and most never get any engagement. It occurred to me that people might want a better way to do this, and bringing them together in a niche social site might help.
So I made Wax Spinner. Connect your Discogs (the de-facto vinyl collector's catalogue) account, post whatever you're playing with an optional note, and it lands in a feed where people can like it and comment. You can also browse anyone's full collection on their profile, and filter the feed by genre, pulled straight from Discogs metadata.
The conversation and the discovery are the primary purpose.
The details this crowd might find interesting: every spin generates its own OpenGraph share card on the fly, with cover art, artist, year, and notes rendered server-side and cached. Getting it to actually display everywhere took way longer than building it. next/og (Satori) only outputs PNG, and the ~800KB it produced was silently dropped by some crawlers' image-fetch limits, so I re-encode to a ~95KB JPEG with sharp. Slack was the biggest hurdle, and as it turned out, my global security headers (X-Frame-Options, CSP) were attached to the image route too, and Slack's proxy refuses to embed anything that signals it can't be framed. Also had to serve the image from a clean static-looking path instead of a query-stringed API route, because Slack's fetcher is oddly picky about URL shape. It now unfurls properly on Discord, iMessage, Facebook, Bluesky, and Slack.
The stack is Next.js (App Router) on Vercel, Supabase for Postgres and auth, Discogs API for collection data. Known limitation: collection import uses an app-level Discogs token, so it only pulls public collections, no per-user OAuth yet.
It's free, no ads, not selling anyone's data. Side project, not a startup, so I'd rather have honest feedback than signups. It's brand new and quiet right now, and a social site is nothing without people in it, so I'd love to hear what's confusing, what's missing, or what would get you to actually open something like this on a Sunday afternoon when you put a record on.
I don't code full-time anymore, but I used to build dating websites in the early 2000's (php, mysql). I used Claude Code to build this as a side project.