Apologies to anyone who’s seen an uptick in twtxt pings from me today… I’ve been working on shoe-horning my twtxt reader (TwtStrm) into my editor (TwtKpr, aka the express-twtkpr npm library), and it kind ran amok a few times. So again, sorry - I’ve added a minimum 10-minute cool-down period between pulls which should help (I hope 🙂).

@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

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).

@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).