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 believe there are! I consistently hear good things about KEXP and FIP but I haven’t listened to either extensively.

I listen to a lot of SomaFM (free, https://somafm.com/) and the Flow State radio-podcast (paid, https://www.flowstate.fm/).

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.

It reads to me like encryption is handled one layer below this by NFS. I would naively assume this should be set up with external changes disallowed since it is capturing and replaying fs events.

I would love to see a replacement for syncthing though. Something with less config knobs, that 'just works' and handles conflicts more intelligently.

Any recommendations on where to source BPA-free thermal paper? I've tried to source BPA free shipping labels in the US and found them unobtainable.

That sounds like this with inline dictionaries added unless I’ve misunderstood you.

I built something quite like this with epubs for another read it later service. There are lots of them!

I wonder if they’d be willing to sell it to the right group of folks. I’d love to have a community owned read it later service. Otherwise, we’re all on a never ending treadmill from one service to the next.

Same here. I get a massive amount of value out of writing things down at home and at work. I get comparably little value out of linking things together — beyond direct references at least. I think this may be a difference in how different people think and recall information.

I’m surprised that they only ran the measurements ten times. Hard to trust any data in this post given it is certainly deficient.

This looks very cool! I see a lot of Python in the docs; is it usable in other languages?

This is unfortunately not emphasized with many breakout boards. It pays off to skim errata sections at the start of a project. All hardware has errata, and it ranges from incorrect details and minor malfunctions all the way through to broken peripherals and all manner of critical malfunctions.

There are industrial knitting machines, but they’re orders of magnitude more expensive, heavier, and tied to closed software ecosystems. They’re extremely capable, but they’re also far outside the hobbyist realm. The only real evolution on these old hobbyist machines is the Kniterate at $16k and 600lbs.

Same, and I add one even more amorphous criteria, 'not directly next to noise pollution like an airport or highways.'

I have not observed this to be true. Ventilating enough to keep CO2 low means sub 20% winter humidity in multiple places I’ve lived.

Fewer people will walk when infrastructure prioritizes drivers and makes it uncomfortable and unsafe to walk. This isn’t the only option.

Cars being built for pedestrian safety is one piece of that picture. As you note, impact safety falls into this category and provides limited benefits for collisions at speed. There’s a lot more to that story though, as we can see in societies that value pedestrian lives. Automatic braking and avoidance, driver attention monitoring, and speed limiters are all options. Add in safe infrastructure, safety enforcement, etc.

There’s a broad range of tools available to reduce pedestrian deaths. None are perfect, none apply universally, but we should consider all of them.

You may also enjoy the Expeditionary Force series. Totally different story, but it has a similar vibe.

Someone built this! https://railforless.us