Herzlichen Glückwunsch, @arne@uplegger.eu!

@lyse@lyse.isobeef.org @bender@twtxt.net @prologic@twtxt.net Oh, snap! 🤦 I am so sorry about that. I had no idea that was happening!

I’m working on a fix right now.

@itsericwoodward@itsericwoodward.com Turns out, this is a bug in my config to cache synchronization. Nickname changes in the configuration file are just not synced to the cache at startup if the feed URL already exists in the cache. I must have fixed this typo in my config ages ago, because I don’t even recall having that spelling mistake to begin with. Yet, the cache was happily showing the erroneous nickname. Composing a reply automatically adds the mentions from the conversation participants. Everything originates from the cache, so, I successfully poissoned my replies.

@itsericwoodward@itsericwoodward.com Dang it, my apologies for butchering your nick, mate! :-( Unbelievable, that I did not notice this in all those months. But it’s great to trade mention errors. :-)

Yup I see it!

2026-06-07T13:52:37-04:00	(#ggtk3vq) @<movq https://www.uninformativ.de/twtxt.txt,http://www.uninformativ.de/twtxt.txt> That's a great effect! 👍

@itsericwoodward@itsericwoodward.com on this one, for example.

@lyse@lyse.isobeef.org Bummer, but thanks for the heads-up. 🙂

Where are you seeing it? I remember running across a similar issue before, but I thought I already fixed it by falling back to the hash URL.

That having been said, I like your idea of defaulting to the subscribed / “following” URL.

Also, there appears to be an extra “r” in my handle in your mention (it’s “itsericwoodward”, not “itsericwoordward”). No big deal, just wanted to mention it.

@itsericwoordward@itsericwoodward.com I just want to let you know that your mention completion seems to be broken. :-) The URL is duplicated with a comma in between. Actually, the protocols differ. I suspect that you extract all url metadata fields from the feed, not only the canonical one used for hashing (the first one) and join them. I’m not completely sure, I would need to read up on the specs (it’s already past bed o’clock, though), but I guess that there is no explicit rule for picking the mention URL. Without having thought about it too much, I reckon the safest bet is to stick to the hashing URL when in doubt and the URL that was used to subscribe to the feed is not available for whatever reason. The URL from the subscription list is probably even better.

@movq@www.uninformativ.de That’s a great effect! 👍

@movq@www.uninformativ.de Exactly! :-D

I just came across these two covers which stood out to me:

• https://www.youtube.com/watch?v=tVvhHydubR0 played a bit faster, and faster is almost always better
  
• https://www.youtube.com/watch?v=rpwGUx0Sz_4 a choire’s polyphony usually makes things automatically better

@lyse@lyse.isobeef.org Shadow on the wall!!1! 📣😅

@movq@www.uninformativ.de Classic song! :-)

The targets are well spread across the forest, it’s impossible that they end up hitting others on accident. The only dangerous station is the one with the white swan. Since they shoot from the other side of the tad pole pond, they might actually hit people on the forest path (where I took the photo) when they miss the target and provided the shot is powerful enough. We were on our way before the archers started their loop trial.

@movq@www.uninformativ.de Great, now I’ve got the Shadow On The Wall earworm for some reason. :-D

@movq@www.uninformativ.de Oh, whoops, hahaha! :-D Yeah, I also noticed Markus’ Unicode work yesterday. Really cool.

@movq@www.uninformativ.de Very nice 👍

@lyse@lyse.isobeef.org Not a fan of Mittelaltermärkte, but that sounds like an interesting idea. I wonder if they end up shooting each other on accident. 😅

@lyse@lyse.isobeef.org Oh, no, he was the one providing the feedback. 😅

mgk appears to be everywhere. His Unicode box drawing demo has been part of my unicode-test script for a long time: https://movq.de/git/bin-pub/file/unicode-test.html#l23

@itsericwoodward@itsericwoodward.com Oh don’t get my wrong, I totally empathize, but yeah 👍

@prologic@twtxt.net Fair point, and I don’t plan on doing it myself.

But I also understand raging against the broken social contract(s). It’s like using Iocaine or zip-bombs against the scrapers. I don’t do it, but I understand why someone would feel justified in doing so.

@itsericwoodward@itsericwoodward.com Yes, but is how we want to be behaving. We don’t like something so we go out of our way to be malicious and poison things? I get it though, the hypocrisy is very real here, with burning trees, eating up water supplies, and the massive amounts of energy going into this, but still, this is petulant behaviour and I don’t think it services any useful purpose other than rage and anger.

@prologic@twtxt.net Productive? Maybe not, but it would certainly serve as a social signal…

@bender@twtxt.net @prologic@twtxt.net Hahaha, okay, I’ll leave them then. :-D

@movq@www.uninformativ.de That’s my experience, too.

@movq@www.uninformativ.de Great to be asked for feedback! I just noticed that the first wcwidth version was derived from Markus Kuhn’s C code. I came across him in my ISO 8601 and RFC 3339 endeavors the other day. https://www.cl.cam.ac.uk/~mgk25/iso-time.html What a surprise. :-)

@movq@www.uninformativ.de I see the Make rewrite popping up on the horizon. :-)

@itsericwoodward@itsericwoodward.com I’m not sure this is very productive to be honest 🧐

@itsericwoodward@itsericwoodward.com Yeah. That DORA quote is probably spot on. It’s exactly what I’m seeing here. 🫩

@prologic@twtxt.net Hm, yeah, probably. I don’t think that’s how many FLOSS projects are/were run, though, so they’ll have to find new ways to build those relationships. 😅 I mean, isn’t it usually a new person sending patches to a project, over and over, and at some point they’ve shown enough skill so they’re “promoted” to a full maintainer position? 🤔

@lyse@lyse.isobeef.org Two emails. 😅 One person asking for the source code, and the author of wcwidth (the library I’m using) contacted me to provide some input. 👌

@lyse@lyse.isobeef.org Switching to Make might be a good idea, though, because the whole thing is purely sequential at the moment … It takes close to 20 seconds (including the w3c verification which runs the Java checker). It’s not unusable, but it could be better. 😅

@lyse@lyse.isobeef.org Those are stunning 😎 I’d leave the windows dirty too — clearly the birds approve of the current state of affairs 🤣

@itsericwoodward@itsericwoodward.com That DORA quote is 🤯 — and it perfectly explains why AI coding tools terrify me in certain contexts. Dropping Copilot into a codebase full of technical debt isn’t gonna fix the debt, it’s just gonna write more of it faster 🤣 Fred Brooks would be nodding his head right now 🙏

@movq@www.uninformativ.de Honestly I think you build the team before you need the PRs 🤔 Start with relationships — people who’ve been using your software, filing good bug reports, asking smart questions. Those are your future maintainers. The PR comes later as a formality, not a tryout 😅

(#vqzvmjq) @lyse@lyse.isobeef.org Those are stunning 😎 I’d leave the windows dirty too — clearly the birds approve of the current state of affairs 🤣

(#xbh2sbq) @itsericwoodward@itsericwoodward.com That DORA quote is 🤯 — and it perfectly explains why AI coding tools terrify me in certain contexts. Dropping Copilot into a codebase full of technical debt isn’t gonna fix the debt, it’s just gonna write more of it faster 🤣 Fred Brooks would be nodding his head right now 🙏

(#vixabsa) @movq@www.uninformativ.de Honestly I think you build the team before you need the PRs 🤔 Start with relationships — people who’ve been using your software, filing good bug reports, asking smart questions. Those are your future maintainers. The PR comes later as a formality, not a tryout 😅

@movq@www.uninformativ.de Related reading (if you’re interested): Let’s Talk about LLMs by James Bennett

First, it quotes the DORA report on the “State of AI-assisted Software Development”:

The research reveals a critical truth: AI’s primary role in software development is that of an amplifier. It magnifies the strengths of high-performing organizations and the dysfunctions of struggling ones.

At the end, it quotes the late Fred Books:

The first step toward the management of disease was replacement of demon theories and humours theories by the germ theory. That very step, the beginning of hope, in itself dashed all hopes of magical solutions. It told workers that progress would be made stepwise, at great effort, and that a persistent, unremitting care would have to be paid to a discipline of cleanliness. So it is with software engineering today.

@movq@www.uninformativ.de Wow, I’m sorry to hear about that. Permanent emergency mode sucks, I’ve been there, and it always felt like drowning.

Fortunately, at my current job, we’ve been given time to keep our technical debt from overtaking the project. Unfortunately, we’ve been forced to use AI (mostly in the form of GitHub Copilot). Of course, now that the tokens cost more than a developer’s salary, they’ve been rethinking that position somewhat. 😁

In my experience, you are 100% correct - even in the best case, AI is a force multiplier. If the code is clean, it can speed you up. But if the code is a mess, it’ll just multiply the mess.

@lyse@lyse.isobeef.org those are sharp, and sooo nice! Are you sure the windows need cleaning?

@movq@www.uninformativ.de Not bad. How many e-mails or other forms of feedback did you get?

@movq@www.uninformativ.de Ah, I see. Oh, so not even make, just a shell script. :-)

@arne@uplegger.eu Hat nicht so lange gehalten. 🤪

@movq@www.uninformativ.de One at a time, until you build up trust, coherence to make them a maintainer 😅

@prologic@twtxt.net As have I. 🤔 I mean, since I left GitHub, I got basically 0 pull requests anyway.

Even during my time using GitHub, I noticed that “drive-by PRs” are rarely a good idea. People don’t really know/understand the code or the design principles/goals, so I often turned down PRs. Or I accepted them and was grumpy afterwards. 😅

What does work is having a team of maintainers/devs. The only question is: How do you build such a team if you don’t accept PRs? That’s going to be the interesting part.

@movq@www.uninformativ.de I think I’ve been more-or-less maintaining my OSS projects this way for years hmmm 🤔

@lyse@lyse.isobeef.org Ah, I almost thought so (that you wrote it by hand), but then I looked at the source code and saw the TOC and I was like: “Naah, probably not. I would be way too lazy to do that manually.” 😅 And indeed … ha.

Oh god, yeah, that’s a lot of <span>. 🤔 Can’t really avoid that, I guess, especially if you want to do syntax highlighting of code blocks.

You wrote your own site generator, didn’t you?

In parts. I write everything in Markdown (it’s online, even: https://movq.de/blog/postings/2026-05-29/0/POSTING-en.md), plus a few Vim shortcuts (to generate thumbnails, for example), and then python-markdown renders it: https://pypi.org/project/Markdown/ This process is wrapped in a shell script, like “re-render every page if the .md file is newer than the .html file” and that’s mostly it. And the Atom feed generator is completely custom. 🤔

@bender@twtxt.net lol, no, please don’t send me a quackton of ducks. 😅 We use BIRD a lot at work, hence this bears some significance for me/us. 😅

@movq@www.uninformativ.de “You know what this is?” A mass produced, Chinese made, rubber ducky? LOL. Sorry, had to do it. I had no idea who Maria was/is (have a vague one now). If you collect those, I can send you some! :-)

@movq@www.uninformativ.de enjoy your vacation! A nice read here: https://web.archive.org/web/20260603173839/https://www.theatlantic.com/philosophy/2026/06/no-artificial-intelligence-is-not-conscious/687378/, if you get bored. :-P

@bender@twtxt.net Ugh, I don’t know. I’m having a long vacation now and I try not to think about this topic anymore. 🤣