@itsericwoodward@itsericwoodward.com noticed absolutely nothing. Happy developing!

@itsericwoodward@itsericwoodward.com Excited to see twtxt tooling in the Node ecosystem! Any plans to implement the Twtxt v2 extensions? Things like Twt Hash + Subject (proper threading), Multiline, etc. — all documented at https://twtxt.dev 👀

@itsericwoodward@itsericwoodward.com All good here 👌

@bender@twtxt.net Thank you, we think so too.

I’m glad you like it!

@itsericwoodward@itsericwoodward.com that second one… 😍! Shadow is such a handsome boy!

@movq@www.uninformativ.de Hahaha, a ride indeed. Exactly, this affected each and every Atom feed and only Atom feeds. All RSS feeds worked like nothing ever happened. This std::string to time_t to std::string to time_t dance only happens for Atom feeds. RSS feeds, on the other hand, go right from std::string to time_t and be done. That’s precisely what the second option is aiming to propose for Atom feeds, too.

I will clarify that tomorrow in the article.

It’s very interesting what kind of quirks accumulate in software over the years. Especially quirks, the basically noone knows of anymore. Until something explodes and gets rediscovered. Luckily, that doesn’t happen all that often.

@lyse@lyse.isobeef.org Oh, nice. That was quite the ride. :-) And all that because of locales. 😳

But, did I understand that correctly? All Atom feeds were broken, right? Because they all use that same code path with that strftime/strptime dance in it?

@bender@twtxt.net No way, impossible! Which pattern could you have possibly spot? :-D

@bender@twtxt.net Doesn’t happen often. And when it does, it’s a matter of just a few minutes.

@movq@www.uninformativ.de Oh yes, very cruel. Absolutely. But also beautiful sometimes.

@movq@www.uninformativ.de Wow, quite the background noise! I like the birds, though. :-)

@lyse@lyse.isobeef.org love them! I hunt for those here. I enjoy watching it as it happens. Never that red, though.

@lyse@lyse.isobeef.org I notice a theme here, but can’t quite place my finger on it… 🤭

I wasted my entire weekend on the writeup. If you have way too much time to spare and also are interested in a bug analysis of a software that you don’t even use, I have you covered: https://lyse.isobeef.org/newsboat-time-parsing-bug-analysis/

@movq@www.uninformativ.de that was lovely! I especially liked the rain. I truly am a sucker for rain!

Ambient noise. Crows, (wild) parrots, pigeons, the occasional blackbird, some traffic, individual raindrops, thunder, heavy rain on lots of trees.

A welcome change from the daily noise of the construction site nearby.

(I wish I had better equipment. As usual.)

https://movq.de/v/9b7df4ea0a/2026-05-31–regen.flac

Last minute entry for #caturday (at least in this time zone)…

This is Shadow. He’s an incredibly sweet boy who likes long walks (on your shoulder), loving on his puppies, and laying in his bowl(s).

https://itsericwoodward.com/images/17a03702.jpg https://itsericwoodward.com/images/c4b3ce57.jpg https://itsericwoodward.com/images/4bbc4698.jpg

@lyse@lyse.isobeef.org It’s OK, it’s still WIP. You’re just helping make it more robust. 😁

@arne@uplegger.eu I’m similar… I use “I” most of the time (mostly in planning or trying to focus, ex: “I’m going to do X, then Y”), but I also use “you” when fussing at myself for my perceived faults or mistakes (that’s my “lizard brain”, we don’t get along so well because he’s kind of a jerk).

@prologic@twtxt.net you went to sleep so early! It’s barely 14:19. 😂

@lyse@lyse.isobeef.org Nature is cruel.

And the humidity sucks. It’s been a horrible day. 🥴

@prologic@twtxt.net Jesus, that’s expensive. 🥴

@bender@twtxt.net LOL 😂

@prologic@twtxt.net my gosh, that’s some expensive lottery! I have the feeling I would win, but I never play. 🤭 Wife, on the other hand, does. East and west coast, with a bunch of her friends (a pool). They win nothing, for many years. 😅

@movq@www.uninformativ.de $95 🤣 So I’m down a fair bit 😳

@prologic@twtxt.net lol, well, better than nothing, eh? What did the tickets cost? 😅

Oh, nice. In my endeavors of time in C++, I came across cal 9 1752. https://www.redhat.com/en/blog/brief-history-mktime

@movq@www.uninformativ.de I came across that in some of these threads, too. I should probably give OpenRsync a shot.

Oh boy, it was bloody humid this morning. Just around 20°C when we left, but climbing rapidly. The flow of air when walking was okay, but as soon as we stopped, streams of sweat were pouring down on us. Luckily, it was cloudy, but the lack of wind was bad. Now, the sun is out, 29°C will be reached in an hour and I’m glad that the house is still cool. It will be a different story in a few weeks or months. Not looking forward to that at ll.

On the bright side, we saw the first tadpoles of the year and an also first, but sadly dead slow worm that probably some bird dropped on a bench next to the fountain. The fly was stuck to its feast and also cactus. The municipality fixed the railing nicely and we came across a giant patch of great looking fire bugs on the summit.

All in all, a successful stroll through the woods but for the humid heat.

https://lyse.isobeef.org/waldspaziergang-2026-05-30/

@movq@www.uninformativ.de I guess I’m not so lucky haha 🤣 Only won $32 AUD 😅

@lyse@lyse.isobeef.org @tftp@tilde.town Someone has pointed out that there’s OpenRsync:

https://www.openrsync.org/

Since I run OpenBSD on my servers, I actually do use that and have never noticed any incompatibilities with the “normal” rsync.

These nicely lit jet trails are the work of the sunset: https://lyse.isobeef.org/abendhimmel-2026-05-22/

One and a half weeks ago, our sunset delivered strong colors: https://lyse.isobeef.org/abendhimmel-2026-05-21/ Apologies for the damn fuzz in the optics.

@bender@twtxt.net I’ll think about it. :-)

I rode my bicyle to the scout flea market setup a few weeks ago when I had to stop to admire the morning sun lighting up the fields. https://lyse.isobeef.org/morgensonne-2026-05-08/ Of course, these photos don’t do justice at all.

@movq@www.uninformativ.de Hah 😅

@movq@www.uninformativ.de Hah 😅 One thing I’ve learned in my life (as I’ve had many good manegers over the years teach me as much) is:

Strong opinions, held loosely.

I have my opinions too, but I also see positives and benefits and I am optimistic that we will collectively figure out a path forward.

Haha, someone had a similar idea … https://lpcvoid.com/blog/0018_why_i_am_against_genai/index.html

@prologic@twtxt.net You actually did? 😅 Good luck. 😅 I never dared to, I’d probably get addicted. 🤣

@movq@www.uninformativ.de Amen 🙏

@prologic@twtxt.net Oh yeah, same here. 😞 Let’s all just win the lottery and stop with this damn work thing. 🤣

@movq@www.uninformativ.de All good, I’m tired too. Work has been burning me out lately 🥵

@movq@www.uninformativ.de Yes 👍

@prologic@twtxt.net (I hope I’m not too incoherent. I didn’t sleep very well recently and have a lot of unrelated stuff on my mind. 🤣)

@prologic@twtxt.net Ah, so that’s what “Bob” is. I saw that popping up in email notifications. 😅

@prologic@twtxt.net

it’s “probabilistic” not “deterministic”

Yep, I know. And when I tell that to people and tell them “if we use AI here, we lose the ability to debug this stuff”, then all I get is: “But it’s good enough. We don’t need to debug this. Non-deterministic computing has its use cases.”

But that is just not how I’d like to model/implement our business processes. 🤔 I want something reliable, not “it mostly works”.

It’s one of the reasons in fact I’ve been working on bob so I have a very concrete and strong foundation for how these things work, how they behave and how bad or good they can be. I am on-purpose building bob to be not only a decent coding tool and general task completion tool, but with serious security boundaries, sanitation, auditing and compliance. If I’m going to succeed at building autoonmous agents that can cope with a wider array of varying inputs (mostly natural language, some structural language) then it needs to be both a) Safe and b) Robust

@movq@www.uninformativ.de I’m kind of flag you bring thi sup, because you simply can’t. You wouldn’t even be able to in an atypical neural network either (which is what ehse things are anyway). The problem here really isn’t the so-called “AI” (I wish we’d stop calling it AI), but the flawed usage(s) thereof. I believe I even stated earlier in this thread that sometimes it may not do what you expect, it’s “probabilistic” not “deterministic” – those pushing for greater use need to understand this, those not happy with the “push”, should educate the ignorant here (especailly managers pushing for weak, insecure and bad uses).

@prologic@twtxt.net Ahh, I see. Okay, I’m with you there. On this high level, I can understand how the thing works.

Maybe my wording isn’t good. 🤔 Let’s take a real life example from what we do at work.

There’s this AI chatbot. It gets support requests from users, so the user says something like “I need access to a particular system”. This triggers the bot to “run” the instructions stored in a large Markdown file, like “check if the user is authorized to do this, then issue the following API requests”, and so on. This is essentially like running a little script, except it’s written in natural language (German) and there’s no “script interpreter” but just the AI.

Now, suppose that the AI doesn’t quite do what was intended. There’s some subtle bug. How do you debug this? How do you find out how the AI came to the “conclusion” to run step A instead of step B? And how do you find out how exactly you have to change your prompt so this doesn’t happen again next time?

If this was an actual script/program instead of AI, you could repeat the request and attach a debugger or throw in some printf() or whatever. How do you do that kind of thing with AI? How do you pinpoint exactly what the problem was?

(Or is this just a stupid idea? Do we have to give up that way of thinking when using AI? Is the era of debuggability over?)

@movq@www.uninformativ.de I think your points are pretty clear to me, that’s fine. I’m just seeing if you can perhaps see things a different way maybe?🤔 I would challenge the assertion that you cannot understand how Claude Code generated an output; which I can demonstrate easily with a fairly trivial example by the input:

Write a program in Go that sums a list of numbers from stdin and prints the result.