wilted-iris

It’s the unified interface for me. Updates, logs, service management, network routing, config and storage mapping are all uniform and I don’t have to wrangle many slightly different implementations of each. Isolation from installed packages is a nice bonus.

Yes! This launched after I left Spotify but I agree it looks neat. I find the three month build expiration concerning, but I also have a low risk tolerance for my music experience.

Have a look at the librespot pinned issues, you’ll see the reports from folks experiencing this. You may also be able to find the legal threats they sent out to third party client libraries if you search carefully (many have been redacted.)

Librespot no longer works for new accounts. APIs are being gated off and they’re applying legal pressure to dissuade projects from reverse engineering anything new. At the end of the day, they can turn the tap off anytime they want, whether by technical or legal means. I tired of having so much of my music experience at risk and chose to migrate on my own terms.

I listen to Flow State, SomaFM, and aggregate from local shows and a few people I follow on social media among other discovery platforms. (I don’t have a favorite yet.)

I found that Spotify was increasingly recommending AI artists and songs I already knew. It surfaced very little outside of my comfort zone and effectively nothing that wasn’t new. There’s a whole world of music out there that Spotify wasn’t showing me.

Spotify is in the process of killing the librespot project that this and most third party Spotify players are built on. I think the golden age of music streaming is coming to an end. I’ve migrated to a self hosted library with streaming and radio for discovery. I hope we’ll see many projects in the space flourish. Many, like Navidrome and the whole OpenSubsonic ecosystem, seem to be doing quite well.

These look great. I wish they had existed way back when I did embedded work every day. What was the process like to create them? Did you design them from scratch, get them built to spec, something in between?

The switchable host is interesting to me. What do people use that for?

I’m curious, does the addition of wireless enable anything that wouldn’t be possible on RS485? Naively to me, it seems like it would add failure modes and hurt worst case performance, but I assume it’s a tradeoff to get a bandwidth or average latency improvement.

Respectfully, no, not even a little bit. That’s normal everyday microcontrollers for you.

Worth noting that kobo devices are not locked down at all and run linux. They’re very easy to build for.

This looks interesting and I'm curious if anyone has more context for why it's on the frontpage today.

International airports as well.