Agents don't know to not put easter eggs in the release notes:

    •  /buddy is here for April 1st — hatch a small creature that watches you code

UnitedNuclear has these and a bunch of other interesting tidbits if anyone wants to give it a try. I bought a small bottle of heavy water as well, which I of course sampled and can confirm it has a slightly sweet taste to it.

You really have to get your eyes adjusted to the dark to see anything with the spinthariscope. It ends up looking mostly like static on a green crt, but if your only reference frame is a cloud chamber, the volume of particles that are emitted from such a weak source is pretty remarkable.

Lighter, smaller, cheaper, greater efficiency, improved agility.

This is where the cost came from.

>The reference implementation is JavaScript, whereas our pipeline is in Go. So for years we’ve been running a fleet of jsonata-js pods on Kubernetes - Node.js processes that our Go services call over RPC. That meant that for every event (and expression) we had to serialize, send over the network, evaluate, serialize the result, and finally send it back.

But either way, we're talking $25k/mo. That's not even remotely difficult to believe.

The link to the changelog on the page got me wondering what the change history looks like (as best we can see).

I asked chatgpt to chart the number of new bullet points in the CHANGELOG.md file committed by day. I did nothing to verify accuracy, but a cursory glance doesn't disagree:

https://imgur.com/a/tky9Pkz

> "Can I tell you one more thing from your X,Y,Z results which is most doctors miss ? "

I just noticed this for the first time this week (it only happens to me on Instant mode).

Yuck.

If there’s one thing I’ve entirely handed over to our AI overlords it’s the ffmpeg command line.

I have a feeling beamforming microphone arrays might help here, something like this could improve the audio being processed substantially - https://www.minidsp.com/products/usb-audio-interface/uma-8-m....

That's a good call. I have a PS3(?) mic/camera that I was using when I was running the original Mycroft project on a Pi. I wonder if that would help with the inbuilt HA mic not waking for most of my family, most of the time. I will have to look at my VA Preview device and its specs later because I'm not sure if you can connect an external mic to it out-of-the-box.

Alexa devices have these (or used to at least), but Google Home's never did. So it shouldn't be necessary.

Yeah a small (ideally personalized) wakeword model would probably outperform just about any audio wizardry.

I did a bit of a deep dive into motor control and actuators in building a two axis gimbal for tracking satellites with an RF antenna (with the eventual goal of building a mount for optical tracking).

Ben's vids were kind of mind-blowing for me at that time. I couldn't believe some of the control that was possible with relatively pedestrian electronics. Aaed's vids do a wonderful job of making it accessible in an applied way.

It's something I think a lot of the folks on HN would find interesting to tinker with. Nice mix of software and hardware that actually does work in physical reality. It also gives me a level of appreciation for the advances in humanoid robots that I don't think I would have had otherwise. (If you *do* get into it, I'd highly recommend getting into field oriented control with brushless motors and encoders. Small hobby servos are fun but they encapsulate a lot of the interesting parts and tend to have limited options available for things like the capstan vid linked above)