Actually, I’m stupid: I’m using the normal rsync on OpenBSD as well.

And regarding OpenRsync’s general usability:

https://marc.info/?l=openbsd-misc&m=178090751524547&w=2

Right now openrsync is limited in functionality and is primarily present
for rpki-client. The limited functionality makes it unusable for generic
use and so any diff or change like the above will not be considered since it
is simply not ready.

First problem to solve is to remove the mmap usage in openrsync. After
that modern protocol versions need to be added. Once that is in place one
can start a discussion about using openrsync as a default on OpenBSD.

@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

Love this remix:

https://www.youtube.com/watch?v=TfviPc4ag3A

@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 👍

It was an easy patch, so menus have drop shadows now:

https://movq.de/v/73af48a2d2/s.png

Not that big a difference in the dark theme, though.

@movq@www.uninformativ.de Kann mir gleich sein. Ich habe das Album nun daheim. Das kann mir nun keiner mehr nehmen!

@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

For this week’s (slightly late) #caturday, I’d like to introduce our 4th and final feline resident, the old boy we call Bugsy. He’s been with us for 8 years, and we think he’s 13-14 years old (but he’s not saying).

He used to sound a bit like a cartoon gangster (hence the name), but as the years have passed, he started to sound more like late-stage William Hickey (Uncle Lewis from Christmas Vacation).

He’s our sweet little old man, and he is loved.

https://itsericwoodward.com/images/b6baaadd.jpg

A good article on AI: https://www.theatlantic.com/philosophy/2026/06/no-artificial-intelligence-is-not-conscious/687378/

@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…

I was just about to stop my feature freeze and include standard.site in the IndieConnector. Almost.https://maurice-renck.de/en/blog/2026/indieconnector-and-standard-site

@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 🧐

We came across lots of animals in our woodland. There’s a medieval market this weekend in the neighboring town and they use these targets for the bowmen.

https://lyse.isobeef.org/waldspaziergang-2026-06-06/

Well, that might work… https://codeberg.org/awful-systems/AAA-NO-SLOP.md 🤣

@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?

I might have to clean windows tomorrow. https://lyse.isobeef.org/voegel-2026-06-05/

@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. 🤪 https://movq.de/v/1359841828/s.png

I am about to start working on #IndieConnector version 3, and I need your help! In this post, I describe what I plan to change and would like your feedback and ideas. So if you are a user or you want to use it, please let me know what you would expect from the new version.#kirbycms #getKirby https://maurice-renck.de/blog/2026/planning-indieconnector-3

@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 🤔