I need to know about movie improvements
2026-Feb-25, Wednesday 02:25 pmAre there *any* movies which would not be improved by the addition of Godzilla?
![]()
Sophia spent a chunk of Monday evening writing up her half term week
without having to. Her handwriting is already better than mine.
Original
is here on Pixelfed.scot.
https://dotat.at/@/2026-02-24-nsnotifyd-2-4-released.html
The nsnotifyd daemon monitors a set of DNS zones and
runs a command when any of them change. It listens for DNS NOTIFY
messages so it can respond to changes promptly. It also uses each
zone's SOA refresh and retry parameters to poll for updates if
nsnotifyd does not receive NOTIFY messages more frequently. It comes
with a client program nsnotify for sending notify messages.
This nsnotifyd-2.4 release includes a new feature and
some bug fixes:
The new -S option tells nsnotifyd to send all SOA queries to
a specific server.
Previously, in response to a NOTIFY message, it would send a SOA query back to the source of the NOTIFY, as specified by RFC 1996.
(Typically, a NOTIFY will only be accepted from a known authoritative server for the zone. The target of the NOTIFY responds with a SOA refresh query and zone transfer. But it should avoid trying to refresh from one of the other authoritative servers which might not have received the latest version of the zone.)
Mark Felder encountered a situation where it would have
been more convenient to fix the address that nsnotifyd sends SOA
queries to, because the source of the NOTIFY messages wasn't
responding on that address.
Since nsnotifyd is intended to work as glue between disparate
parts of a system, it makes sense for it to work around awkward
interoperability problems.
The nsnotify client program was broken and unable to create
NOTIFY messages. D'oh!
I have adjusted the release process so that it works better with
git archive and web front-ends that offer tarball downloads.
![]()
Spent the afternoon at Hugh and Meredith's, where Hugh showed Sophia
how his 3d printer works (and how he makes 3d dungeons out of foam).
Very cool stuff, and they both enjoyed their souvenirs.
Original
is here on Pixelfed.scot.
Zach Sullivan was interviewed on the "Duke's Download" podcast about being openly queer in ice hockey, and his decidedly mixed feelings about Heated Rivalry. I liked listening to what Zach had to say, and was impressed by the thoughtfulness that obviously goes into his answers (I think the podcast host could stand to say less and interrupt less).
February is flying by, the university term-time intensity is very high, my life is work, ice hockey, occasional time with my family. I did switch things up and also try out a couple of kpop dance classes in a relatively light week (the university has a KPop society!) and they were exhausting and fun in the best way. Now to find the time to go back before the end of term.
Ice hockey
( Read more... )
Driving
( Read more... )
Percy Jackson
( Read more... )
https://dotat.at/@/2026-02-16-async.html
I'm writing a simulation, or rather, I'm procrastinating, and this blog post is the result of me going off on a side-track from the main quest.
The simulation involves a bunch of tasks that go through a series of
steps with delays in between, and each step can affect some shared
state. I want it to run in fake virtual time so that the delays are
just administrative updates to variables without any real
sleep()ing, and I want to ensure that the mutations happen in the
right order.
I thought about doing this by representing each task as an enum
State with a big match state to handle each step. But then I
thought, isn't async supposed to be able to write the enum State and
match state for me? And then I wondered how much the simulation
would be overwhelmed by boilerplate if I wrote it using async.
Rather than digging around for a crate that solves my problem, I thought I would use this as an opportunity to learn a little about lower-level async Rust.
Turns out, if I strip away as much as possible, the boilerplate can fit on one side of a sheet of paper if it is printed at a normal font size. Not too bad!
But I have questions...