If it works for you, happy the help you setup a private instance or something. And for in-office use, maybe optimize for quality rather than minimal updates it is now.
Apple TV lets you share with two sets of apple headphones, which is awesome... but I wanted a way to:
* Share to more than two sets * Extend coverage past the (very generous) bluetooth range of AirPods. * Have lossless (albeit 44khz/16bit) wireless audio with audiophile headphones.
I was considering using an esp32, but so happy this exists now! Thanks!
I've got a few questions maybe later with the protocols and stuff but so far from initial look, it seems super promising.
Nice job really!
I thought this was a new Airplay implementation from the way it was described, but then I looked at the source code and realized there wasn’t much there. Nothing wrong with wrapping a library, but it’s nice to mention the technologies used and set expectations.
But it’s a common courtesy to credit the foundations you build upon when they’re doing the heavy lifting for an app.
If you look at the Airstream repo, you’ll see that it prominently credits the underlying library that it uses for a lot of the AirPlay foundational work.
That’s what I was trying to do. I opened up the code, started reading, and realized it wasn’t really what I thought it was.
I’m not trying to “police” arbitrary things, I’m trying to explain what the project is.
There’s been a recent trend of “Show HN” projects taking credit for other people’s work, like the “KVSplit” Show HN from several weeks ago that claimed credit for some upstream features in another project by wrapping it up in a separate repo and writing some LLM-generated claims.
Without massive moderator intervention that whole submission would have been buried in cruft. Better to not start cruftalanches to begin with.