@lyse@lyse.isobeef.org Nice! And I didn’t look out the window at all. Was watching eels. 😂

Well, that was fascinating: https://www.youtube.com/watch?v=LxNq8zOEbM8

@bender@twtxt.net The person actually reached out to me. It’s all good. ✌️

@dce@hashnix.club Oof, that’s surprising. I wouldn’t have expected that to be so slow. 😳😳😳

@lyse@lyse.isobeef.org You might enjoy this one: https://github.com/TheMozg/awk-raycaster

Dear dev.alessandrocutolo.it, do you really need to fetch my twtxt feed every 20-30 seconds? 😅 Not that it’s posing a problem, but I feel like this could be optimized. For example, how about using the if-modified-since request header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/If-Modified-Since

@lyse@lyse.isobeef.org @dce@hashnix.club It’s pretty cool, I won’t argue that, but also really simple, to be completely honest. 😅 The BIOS already provides all you need to send data to the printer:

https://helppc.netcore2k.net/interrupt/bios-printer-services

The BIOS actually does provide a great deal of things, which, to me, was one of the most surprising learnings of this project (the project of writing a little 16-bit real-mode OS, that is). It often doesn’t feel like I was writing an operating system – it felt more like writing a normal program that just uses BIOS calls like we would use syscalls these days.

(I’ve also read a lot of warnings, like “don’t use the BIOS for this or that”. Mostly because it tends to be very slow.)

Good morning. Driving the dot matrix printer from my little real-mode toy OS. 🖨️

(This is just a wrapper around BIOS INT 17. I love it nonetheless. 😅)

https://movq.de/v/6b3f9a2837/MVI_8839.MOV.mp4

Speaking of clouds, yesterday evening: https://movq.de/v/bafe89fd66/p.jpg

Right, now that I’m reading some comments: I was initially assuming that they would actually make it impossible for distros to provide a 32-bit build (intentionally or unintentionally). But maybe that’s not the case and distros can just continue to ship a 32-bit Firefox …

Is that really necessary? How hard is it to make a 32-bit build? 🤔 Honest question. https://blog.mozilla.org/futurereleases/2025/09/05/firefox-32-bit-linux-support-to-end-in-2026/

@dce@hashnix.club Which Thinkpad specifically is this? “Late-2010s” doesn’t sound very old, to be honest, I wonder why OpenBSD is giving you so much trouble. 🤔

@lyse@lyse.isobeef.org Oh no! 😱😱😱

@lyse@lyse.isobeef.org Weather’s great at the moment, isn’t it? I like it when it’s cloudy, dark, chilly. 😊

Ariadne explains some of the reasons behind this “Wayback” thingy (rootful X11 on Wayland):

• https://social.treehouse.systems/@ariadne/115147291885663574
  
• https://social.treehouse.systems/@ariadne/115147331909980717
  

They should put this in a FAQ on their website or something. The whole endeavor makes more sense when you look at it like this.

@bender@twtxt.net I switched back to groff a few weeks ago. 🤪

@zvava@twtxt.net Hooray for more twtxt clients 🥳

@lyse@lyse.isobeef.org (Haha, every time I read the word “Gophers”, I have to stop and remind myself that this is about Golang. 🤪)

@lyse@lyse.isobeef.org I usually only have my GPS tracker with me. That trip yesterday was probably a one-time thing. 😅 It was fun, but I’d rather not carry so much stuff around. 🥴

@dce@hashnix.club Glad you liked it. 😅

@bender@twtxt.net Right. 😂 groff, Markdown, groff. Justified, unjustified, justified.

@bender@twtxt.net Oh, there’s an easy explanation. But maybe some mysteries are best left unexplained. 😃 If you want to solve this riddle: The solution is in the phlog! Somewhere! 😅

@bender@twtxt.net The address is/was correct but probably got mangled by the Markdown renderer. Let’s try again in a code block:

gopher://uninformativ.de/0/phlog/2025/2025-09/2025-09-03--roophloch.txt

@thecanine@twtxt.net I’m seeing those Clippys everywhere now. 📎

@bender@twtxt.net Yeah, the acronym is funny. 😅

Wandering through the woods for 8km … gopher://uninformativ.de/0/phlog/2025/2025-09/2025-09-03–roophloch.txt

@klaxzy@klaxzy.net I’ve had many SD cards die in Raspberry Pis. Really annoying. I’ve eventually switched to using a read-only rootfs. 🫤

I think I’m gonna participate in ROOPHLOCH this year: gemini://zaibatsu.circumlunar.space/~solderpunk/gemlog/announcing-roophloch-2025.gmi

Now that’s interesting. Some of these bots start crawling at URLs like this:

https://uninformativ.de/projects/lariza/NetTracer-Scenes/GPUTracer/multipass/xlonitor/http-collect/getpw

That is obviously completely wrong. But I can explain it. Some years ago, I screwed up my nginx rewrite rules, and that’s how these broken URLs came to be.

It all redirects to /git now, which is why that endpoint sees so much traffic lately.

But what does that mean? Why do they start there? I can only speculate that this company bought an old database of web links and they use that to start crawling. And it was probably a cheap one, because these redirects have been fixed for quite a long time now.

@prologic@twtxt.net I’m doing that now as well, but I don’t think this is a good solution. This is going to hurt “self-hosting” in the long run: I cannot afford true self-hosting where I actually do host everything here at home – instead, I must use a cloud provider / VPS for that. It is only a matter of time until my provider starts doing AI shit as well (or rather, the customers do it) and then what? I get blocked, e.g. I can’t send email to (some) people anymore. This is already bad and it’s going to get worse.

@lyse@lyse.isobeef.org Didn’t know that, either. 😂 The one guy even tried to test this theory with a Polaroid? And “confirmed” it? What the heck. 🥴

@dce@hashnix.club Yeah, I’ve read about that approach. Sounds clever. Truth is, I’m too tired. 😢 I don’t want to spend too much of my time fighting assholes.

I’ve now started blocking entire cloud hosters. Sorry, not sorry.

As expected: Didn’t last long. They’re coming from different IPs now.

I’ve read enough blog posts by other people to know that this is probably pointless. The bots have so many IPs/networks at their disposal …

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

@prologic@twtxt.net Yeah, I’ve blocked some large subnets now (most likely overblocking a lot of stuff) and it has died down.

I’m not looking forward to doing this on a regular basis. This is supposed to be a fun hobby – and it was, for many years. Maybe that time is just over.

“But all your stuff is MIT licensed! They are allowed to do that!”

Haha. As if they would care. They crawl everything they get their hands on.

Besides, that’s not true, the license states that the copyright notice must be retained. “AI” breaks that. They incorporate my code and my articles in their product and make it appear as if it was their work.

Why do I care about this?

1. The load will become a problem at some point.
   
2. These crawlers and the current “AI” in general are breaking the rules. I am supposed to be paying for every little thing, I get sued for “piracy”. But apparently, these rules only apply to me. If I had more money, I could break them. Fuck that.
   
3. I simply don’t want it. Period.

This probably means that I can no longer host my own website. I don’t want to deploy something like Anubis, because that ruins the whole thing: I want it to be accessible from ancient browsers, like OS/2 or Windows 3.11.

I’ll keep an eye on it for a while. Maybe try to block some IPs.

Sooner or later, I’ll take the website down and shift everything to Gopher.

It doesn’t pose a problem for my server’s performance – yet. But if more bots/companies start doing this, my website will go down from the load.

The bots have begun to access my website way more often. I’m getting about 120k hits on https://www.uninformativ.de/git/ now in a couple of hours.

They don’t cache anything, probably on purpose.

It comes in waves. I get about 100 hits (all at once) on that /git endpoint, all from different IPs. Then it takes a moment until I get another wave of about 500-1000 requests (all at once) where they do HEAD requests on some of the paths below /git. I assume they did a GET earlier and are now checking if something has changed.

@lyse@lyse.isobeef.org Best logo ever made. 😅 (It’s partially proprietary software. Just for Epson scanners, I think? Not sure.)

@lyse@lyse.isobeef.org Yeah, that was a lot of fun. 😃 Now let’s wait and see if I ever get to actually use this. 😂

@thecanine@twtxt.net We don’t use Microsoft at work – but similar products of other big companies. They’re all doing the same. The core product gets worse and worse, because they focus so much on vomiting “AI” over everything.

It will die down eventually. I hope.

This is something that @kat@yarn.girlonthemoon.xyz might enjoy:

Recreating the “EPSON Image Scan!” logo with one of my Tux plushies. 😅

@prologic@twtxt.net Enjoy the weekend. 🥳 (I rarely drink these days. I hope my tiny little Whisky collection doesn’t go bad. 😂)

The audacity … how about you keep it, eh?

From: Netflix <info@members.netflix.com>
Subject: Here’s what’s leaving Netflix soon

@dce@hashnix.club Ah, oh, well then. 🥴

My client supports that, if you set multiple url = fields in your feed’s metadata (the top-most one must be the “main” URL, that one is used for hashing).

But yeah, multi-protocol feeds can be problematic and some have considered it a mistake to support them. 🤔

You can fuck right off, thank you very much.

(18/29) upgrading firefox
New optional dependencies for firefox
    onnxruntime: Local machine learning features such as smart tab groups

@lyse@lyse.isobeef.org Yeah, removing the cover will probably help. I’ll have to try. 😅 And, yes, the scrolling is pretty annoying (and kind of ruins the experience a little bit).

The printer isn’t that loud – at least not for a dot matrix printer. 😅 It’s been ~30 years since I’ve last seen them in person, but I remembered these things to be louder. I’m typing on my Model M, maybe that contributes to the perceived noise on this video. Here’s an isolated recording of that keyboard: https://movq.de/v/ddc98b03d8/2022-02-21–model-m-goes-brrr.ogg 🤣 It really sounds like that when you’re typing fast. Brrrrt.

@dce@hashnix.club I switched over to following you on Gopher, because why not. 😅

@thecanine@twtxt.net Oh! 🤯 Hadn’t heard of this before. And 100% agree with that video.

I’ve got a prototype of my hardcopy simulator going. I’m typing on the keyboard and the “display” goes to the printer:

https://movq.de/v/56feb53912/s.png

https://movq.de/v/235c1eabac/MVI_8810.MOV.mp4

The biiiiiiiiiig problem is that the print head and plastic cover make it impossible to see what’s currently being printed, because this is not a typewriter. This means: In order to see what I just entered, I have to feed the paper back and forth and back and forth … it’s not ideal.

I got that idea of moving back/forth from Drew DeVault, who – as it turned out – did something similar a few years back. (I tried hard to read as little as possible of his blog post, because figuring things out myself is more fun. But that could mean I missed a great idea here or there.)

But hey, at least this is running on my Pentium 133 on SuSE Linux 6.4, printer connected with a parallel cable. 😍

(Also, yes, you can see the printouts of earlier tests and, yes, I used ed(1) wrong at one point. 🤪 And ls insisted on using colors …)