My mate and I went on a hike on Saturday to Germany’s probably most famous tiniest hamlet. Well, not even hamlet, much smaller. It’s a farm (087) and a closed train station (088, 096-102). Okay, and four other houses. But that’s it. Durlesbach is known from the old folk song „Auf de schwäbsche Eisebahne“, literally “On the Swabian Railway”. According to the German Wikipedia article the German Folk Song Archive counts about 100 variants on the lyrics with up to 27 verses. The song enumerates a few stations and the most common version is about a farmer who ties his goat to the back of a train in order to save the freight costs. Alternatively, he’s used to that from previous ox cart trips where the goat just follows along. Of course, the goat doesn’t make it and the angry farmer throws the disembodied goat head at the conductor.

The weather was perfect. Sunny and clouds alternating, lower twenty-something degrees Celcius. Very beautiful. We took the train to Aulendorf and started our hike.

The level railway crossing in 051-054 is always closed and only opened on demand. I didn’t even know that this kind existed. But it’s really quiet there. We pressed the lever to call the train dispatcher who then opened the barriers for us. A few seconds later we told him that we successfully reached the other side and he closed them again. We were confused at first because the sign said only for authorized personnel and we were just two random hikers. But we gave it a shot and the dispatcher was super nice, no worries at all.

The river is always the Schussen. 092-094 is the creek Durlesbach, entering the Schussen, though. The Durlesbach station is now privately owned, unfortunately. However, it’s nicely kept in shape and there’s a cool monument with a historic steam engine, two wagons and four bronze figures reenacting the scene where the farmer is about to tie his goat, being observed by his wife and the conductor.

You can get all sorts of drinks in exchange for a donation at the display. These proceeds are used for the upkeep. I had an ACE juice which was absolutely delicious. A few hundred meters after we continued, I thought that I really should have bought a second one. It was just too good.

In Mochenwagen, we took the train back to Aulendorf. The Mochenwangen replacement service (we luckily didn’t have to take it, in fact, no idea when it is really in place) is 800 meters away from the train station. That fucking nuts.

We then changed trains to Ulm, just because that one arrived two minutes after we reached Aulendorf. But we spontaneously exited early in Biberach because we had some time to kill for the actual train to Stuttgart. The train station underpass there has some really beautiful graffiti. Shortly after, my second camera battery was flattened, too.

Going home worked out amazingly. When I switched again in Geislingen, my connecting train was already waiting on the other platform. 15 seconds before scheduled departure, the doors closed. One second to departure, we took off. That’s very rare nowadays and it was kind of magical to witness this first hand looking at the station clock.

Sorry for the many photos. I was busy sifting through them and only kept about 20%. Still too many, I know. Enjoy, nevertheless: https://lyse.isobeef.org/2026-10-03-wanderung-von-aulendorf-ueber-durlesbach-nach-mochenwangen/

@zyak@twtxt.z85b.xyz sorry I just saw this, sounds like a good idea. I’ll see if I can add this!

@zyak@twtxt.z85b.xyz That’s a good idea. I’m updating the twtxt rendering on my site, and I think I’m going to add a toggle to show / hide replies. Thanks!

@lyse@lyse.isobeef.org

Crazy, who comes up with things like that?

I didn’t come up with it, but I was close, I guess. DOS is so small, you don’t have much of a choice but to search for “anything related to time”. There aren’t that many syscalls/functions. You’ll quickly notice that there’s no global tick counter. So what else is there? Hmm, “get the mtime of a file” is pretty much the only other time-related thing. And which file is “stable”, probably allocated just once at boot? Mark Aitchison tried to use NUL, which is a pretty good idea. Thinking about it in retrospect, stdin does indeed make more sense, though, because that object really does get allocated just once at “boot” and then it stays the same. That’s not guaranteed for NUL (although just as likely).

But, it is possible in DOS to move “the console” to a serial port:

I wonder what that does to my little uptime program. :-)

Today, I also learned that -R is an alias for -r in rm.

Ah, I remember that. Dug it up and saved it in the blog: -R is more portable/consistent: http://movq.de/blog/postings/2026-09-30/0/POSTING-en.html

@lyse@lyse.isobeef.org Yeah, the partition stuff with disklabels is what I’m absolutely not used to. I need to invest more time learning this. Not just using it, but how and where is it represented on disk and all that.

I carry my notebook/netbook around a lot. 😅 Watching movies in bed, for example.

I think I’ll stick with NetBSD for a while. It works surprisingly well, it’s new stuff to explore, it’s fast, and then there’s this:

https://mastodon.sdf.org/@netbsd/112446618914747900

Gentoo (https://wiki.gentoo.org/wiki/Project:Council/AI_policy) might be another idea, but I’m afraid that the little netbook might be too slow for that? Or are there binary packages? No idea, it’s been ages since I touched this distro.

(Regarding Linux in general … we all know what Linus said. I’m not sure where this project is heading.)

There is this extremely annoying issue with my website:

https://movq.de/v/4acced3c8e/scroll.mp4

Notice how I’m scrolling, then switching to another tab, switching back, and then the scrolling position is different?

What the hell could cause this? It’s not always like this and I have only seen it in Firefox so far (but I very rarely use Chromium anyway), and this really happens a lot on my site but not on others.

Any ideas? Did I screw up the CSS somehow? 🤔

@movq@www.uninformativ.de That’s a clever idea - I had never considered adding an empty commit before, but I can see the value.

@klaxzy@klaxzy.net This is a good idea. I do something very simialr.

Website might come back soon, although probably mostly unchanged. I have no idea how to stop the bots. 🤷‍♀️ So I’ll just gonna live with it? Is that the key to happiness™? 🤷‍♀️

@david@daiwei.me No idea 🤷 We shall see! haha 😂

Gonna recreate the classic [Break out](https://en.wikipedia.org/wiki/Breakout_(video_game) game this weekend for the Mills Games Cabinet – Anyone else got any ideas, requests? 🤔 #games #ebitengine

@david@daiwei.me Thanks, mate! I just finished my two full version marking gauges. And I’m rather pleased with them, I think they turned out great if I say so myself.

https://lyse.isobeef.org/tmp/streichmass-mit-messerrad/

The beech fences (80 and 100mm long) were part of a former table frame that I cut down. I plugged the dowel holes with, well, dowels. The horrific looking one was the stuck original one, though. Luckily, it’s a hell lot worse on camera than in person. If you take a close look, you’ll also be able to see the large but slight chamfers one one side each that I just left alone.

I really like beech wood. It looks beautiful, is rather heavy (at least in comparison to spruce which I typically use) and thus rock solid, is also a blast to plane and the list goes on. I sanded it with 180 grit and it’s smooth as a baby’s bottom.

The 25mm beech round stocks that house the brass knurled nuts are now roughly 4cm long. That’s one thing I wanted to change right after my first experience. If they were rounded or chamfered more, it would probably be even nicer for the fingers when using the marking gauge. They’re sunken in roughly 3mm in the fences. A forstner bit made quick work. This simplified alignment during glue-up a lot. Will definitely do that again if I happen to build more. I could fully concentrate on the grain orientation and it didn’t shift around.

Just like in the prototype, I used 8mm aluminium solid round bar again for one of the marking gauges. It’s also about 15cm in length. I figure that’s enough. The bought marking gauge has a twenty-something and some change steel rod. So far, all my markings didn’t even exceed probably 50mm.

I found the 8mm brass pipe laying around on the workshop. Didn’t know anymore I had it for ages. Unfortunately, the wall thickness is below a millimeter, so my 6mm wooden dowels are sliding in there. Thus, I put 8mm dowels in my drill chuck and reduced the diameter with a rasp. I went a tiny bit too far, the press fit is on the loose side. When drilling with a 2mm drill (I did that on purpose to hopefully cause the dowel to expand a bit more in the pipe, typically the tap hole for M3 is 2.5mm) and tapping M3, the downsized and glued in dowel slipped down the pipe. Should have used construction adhesive or something along those lines. Anyway, I might replace it with a solid one. I consider this a half-successful experiment. I fear that an unfavorable grain direction might pull out the cutting wheel during use. Let’s see.

The finish of all three is boiled linseed oil. It looks nice, but oh by, this smell. I really dislike it. My hands stink even after washing them several times. I still got several liters left, so I have the dubious joy to use it on many, many other projects to come.

Oh, one last thing. Didn’t manage to drill the tiny holes for my M3x16 bolts perfectly in center like for the prototype. They’re a tiny bit off. Also, on the longer fenced marking gauge, the hole for the knurled nut is a little to the side and at an angle. No idea how I messed this up. Luckily, it’s just a look thing but doesn’t impair use.

Not sure what happened to my twtxt there. It seems that my sync script, which pulls from Codeberg and copies the twtxt to hashnix.club/~dce, had started copying an empty file. No idea why.

It should be fixed now, though, thanks to me adding [ -s /home/dce/twtxt.txt ] && before it copies it to ~/public_html.

@david@daiwei.me Oh, that is a good idea. This could be included here, yeah. 🤔

@prologic@twtxt.net Hmmm, I have no idea how to solve that problem. 😅 Some jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.

I thought I had made that super easy, because you can just send me an email – no sign-up process, nothing. But that’s way too old-school, people don’t know how to use git format-patch (let alone git send-email) and they also don’t understand that they can just send me a link to their forked Git repo (which can be hosted anywhere). Git is super flexible and powerful, but those features are hardly ever used.

Maybe people even need some kind “reward”, or “fame”. Like those “achievements” that you can unlock on GitHub. (Something to put in their CV … ?)

Oh god 🤣 I mean I had this idea to re-invent “Git hosting”, but failed. Maybe I’ll try it again. I dunno. The thing is I hardly get “Issues” really, only when I ask nicely, of folks I know every well 🤣 So think at much “smaller scale” we need a different solution, and I think @movq@www.uninformativ.de is on to something, but not to the extend implemented, somewhere in the middle I think? 🤔

@movq@www.uninformativ.de Hmmm you’ve given me an idea 🧐

@ponderpoints@twtpub.com Welcome to Yarn.social 👋 Interesting video, I actually watched it all the way through, riverting stuff really and quite well put together. The idea of “subjective experience” is a rather complicated thing to describe and you’re right, how do we even know we have them? 🤔

@david@daiwei.me I had to look these up, horror isn’t my genre at all. :-D No idea what the cool kids use today, but I still have zsh as my interactive shell. For shell scripts, though, I try to stick to POSIX and only resort to bash if really needed or it would be too cumbersome.

I trip over this in our code at work all the time.

Python has this concept of “properties”:

class Oink:
    def __init__(self):
        self._foo = 3

    @property
    def my_property(self):
        return self._foo


a = Oink()
print(a.my_property)

my_property() is a method but it can be used as if it were a field.

This can also be used to define a setter:

class Oink:
    def __init__(self):
        self._foo = 3

    @property
    def my_property(self):
        return self._foo

    @my_property.setter
    def my_property(self, value):
        self._foo = 123 * value

Because, for some reason, Python people don’t like getters and setters. Instead, they hide it behind a property.

The result is, when you read this:

a.my_property = 5
print(a.my_property)

You have no idea that this actually calls a method.

@david@daiwei.me That’s a good thing. I still use it heavily, but I also realize that it is addictive. This whole idea of getting likes and boosts is horrible. Seeing “number goes up” is inherently addictive design, if you ask me. This should never have been added to a Free Platform like Mastodon, and I’m glad that twtxt doesn’t have anything like it.

Some further ideas/enhancements for Twtxt App …

• On the “Followers” tab, new followers should appear at the top I thnik.
  
• On the Following/Followers, each feed should be clickable/tappable.
  
  • Maybe also tidy it up a bit, displaying the full raw Feed URI is messy.

Just for security as required by law.

LOL 🤣 Was this someone’s idea of a joke? 🤔

@bender@twtxt.net No idea. I can only tell you that the correct hash would have been rwzz277nkyju for this line:

[2026-07-11 14:47:17+00:00] [(#5bpwpdcjnhcz) <a href="https://yarn.girlonthemoon.xyz/external?uri=https://daiwei.me/twtxt.txt">@david<em>@daiwei.me</em></a> (This thread is broken again on my end. Another bug or fix not released yet? 😅)]

We slept in the forest. It was really great except of my mate’s fucking terror dog who was barking and snarling the entire night to each and every sound. I had maybe half an hour of sleep in total. Despite that, it was pleasantly warm. Well, the night, that is. The heat was brutal during the days. Literally streams of sweat were running down on us on the way there in the evening and back in the morning.

Surprisingly, there weren’t any mozzies around at night, I would have lost all safe bets. On the way there, my mate convinced me to take a shortcut through the taller and taller growing grass. It’s been some time that somebody traveled on this track, so we had to search around a bit for the overgrown path where we could cross the mostly dried up creek. In the beginning I said that this will be a bad idea. Lo and behold, I discovered a tick on my inner upper leg the next morning. Luckily, I got it out with my tick hook on the first attempt.

https://lyse.isobeef.org/walduebernachtung-2026-07-09-10/

@itsericwoodward@itsericwoodward.com what the hell!!? I have no idea how that happened. 😆 Thank you!

I don’t know why, but either Jenny’s behaving different after the last update, or I Fucked up something and I have no Idea how to fix it.

Symptoms:

• I don’t have copies of my New Posts in my Maildir after posting them (as in I don’t see them in neomutt’s inbox).
  
• Nor fetch or fetch context (if they get replied to) seem to fech them auto-magically.
  
• I had to do a full whipe (~/Maildir/twtxt and ~/.cache/jenny) in order to get them fetched back.

@david@daiwei.me Some entries can be probably simplified with just *bot*. :-) (But I don’t use Caddy, so no idea about case (in)sensitivity.

That reminds me, I should do something similar with my Nginx.

@movq@www.uninformativ.de @bender@twtxt.net Indeed! No idea why this isn’t the default in the first place.

The firefly season is ending. I only saw 200 of them or so. There was one female directly on the forest road. If only I brought my camera and tripod, that would have worked out I reckon. I had my torch with me and this looked really cool.

Dusk took forever today. It was really long light out there. Full moon is tomorrow.

On the way back, there was suddenly a load clatter and crashing sound 100 meters away from me. I didn’t see anything, but a tree fell over in the forest out of the blue. Fuck me dead, that was scary as hell. Luckily, I was already on the main road, only meadows around me. It’s the second time I witnessed a tree accidentally coming down. The first one was during the most expensive hail storm in our area so far in 2011 behind me when setting up a summer camp. The weather changed in less than 15 minutes.

Maybe not such a good idea to go out so late alone. :-? Any rustling in the forest immediately reminded me of the boar the other day. Luckily, always false alarm. Still a bit terrified from that event.

@movq@www.uninformativ.de CEF turns out to be pretty easy. I had to write a bit of C and Go to bridge, but once that got going I was able to write it into my pure Go go-wayland wlui library for final rendering. The delegating the entire CEF part was a good idea though because it keeps all the complexity in a container Image, leaving me with just the Go + C stubs/interface and SHM/IPC parts.

@movq@www.uninformativ.de Good idea, I should probably do the same for my photo galleries.

@50213 Star Wars inspires people. (Good) Ideas inspire people. SW is a cultural phenomenon that has inspired millions if not billions of people. That’s why it’s worthwhile.

@prologic@twtxt.net Very cool! Like @movq@www.uninformativ.de, I don’t think I’m the target audience for this (as I’m already a DevOps hobbyist managing a small server “victory garden”), but I love the idea.

Apologies for hitting it early, I initially overlooked the sign-up form and thought I would try it for 💩s and 😁s.

I found my tripod and headed into the woods. There was a ton of glow. \o/ The fireflies were everywhere, super cool. It looked so amazing, especially with all the flying boys. There was one amazing spot in particular, I had 80-100 individuals in my view at once. Absolutely breathtaking. Unfortunately, the mozzies were also delighted about my visit.

I tried my best, but it’s impossible to capture anything on film with my equipment. The fireflies are just way too dim. In the end, I managed to get some very bright girls in the bush. That’s the best I could do, but still really bad. Sorry @bender@twtxt.net. :-(

https://lyse.isobeef.org/gluehwuermchen-2026-06-19/

And no idea what the heck is going on with the CSS there. Anyway. Garbage to trash, seems fitting. ;-)

Getting the vim key bindings to work for focus switching in this modal dialog took me forever. Only cursors and (Shift+)Tab are supported out of the box. I absolutely understand that, it’s fine. I installed an input handler on the dialog, but the focus always stayed the same.

After two wasted hours, I was in despair to copy the tview.Modal into my own code base. Of course, I had to fix all the private tview field accesses first. But even installing the input handler directly on the buttons themselves did not work. Even though, the handler was definitely executed, the focus did not shift. Forcing redraws as a last resort also did not work.

Looking through all the messy chained input handling, I eventually stumbled across another place in the tview.Form, which is internally used by tview.Modal. This messed around with app focus receptions and input handlers. This gave me the idea to make the tview.Application refocus my modal dialog after I told the modal dialog which button to select. And would you look at that, this did the trick! I haven’t completely figured out what is going on exactly, but I could get rid of my Modal clone again.

I always go through hell with focus handling in tview. Each and every time. It just does not feel natural to me. Complete brainfuck to wrap my head around. The Urwid API felt sooo much more refined, it never was an issue. It just works. In fact, I cannot think of any other TUI library that has remotely the same pain level when it comes to focusing widgets as tview.

Now I’m curious how movwin deals with that. ;-)

@lyse@lyse.isobeef.org having seeing, and played with fireflies as a child I envy you. We have none around here. Children have no idea what a firefly is. I mean, they do, but vague, and based on videos and telly.

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

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

Just got a great idea for a novella I will be working on. two other already in the queue. My brian never shuts off!

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

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

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

Now that is an interesting move:

https://ladybird.org/posts/changing-how-we-develop-ladybird/

Maybe this is how all Free Software will look like in the future. It might not be the worst idea … ? 🤔

@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! :-)

Years ago, I used Kate, no, not somebody’s wife, but the KDE Advanced Text Editor, to export source code files and fragments into HTML with syntax highlighting. I think that’s where I got the initial <b> idea from. There were also bucketloads of <span style='color:#644a9b;'> all over the place, even inside <b>. No CSS classes defined upfront, all colors inlined. The final rendering in the browser looked great, but the source code ugly as hell in my opinion. However, I’m thankful for hinting me at <b>. I think this kicked off everything. :-)

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

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

@arne@uplegger.eu This is interesting. Sorry I missed this, I just found this post of yours and wanted to contribute 😅 Here’s something interesting about me… I don’t ever talk to myself, like ever. I have no, what they call, “inner monologue”. Maybe I’m odd, but my wife asked me this very same question a while back and I said the same, there is never anything in my head except ideas, visuals or sounds, sometimes all at once, but never an inner monologue of “talking to myself”.