Haha, indeed:

1. Initial uptime: A bit over 1 minute.
   
2. Changing to serial console, running uptime again: It’s down to 7 seconds.
   
3. Changing back to the VGA console: It’s again down to 1 second.
   

This really doesn’t track the actual uptime, it just happens to “mostly work”. (Like a lot of things in DOS.)

@david@daiwei.me
My email is hey (at) itsericwoodward.com, if that works. While I agree it doesn’t help test federation in the short term, right now I don’t really have a frame of reference for how it should work, which makes it doubly hard to setup. 🙂

TBH, my biggest concerns with running my own instance is with DNS, just because of the “unique” way my home network is setup (plus, it’s always DNS…).

@david@daiwei.me To be honest, I’m a bit tor: part of me wants to set it up on my main application server (alongside gitea, TwtKpr, and a few others), but part of me wants to run it on a Raspberry Pi with Docker (because why not).

I’m also something of a bad geek in some areas, and IRC was never really my scene, so I don’t have a ton of experience with it (I went straight from BBSes to WWW)… Maybe I’ll take you up on that offer of an account at https://chat.ratha.us/, just to get my feet wet… (if it’s still open) 😁

Hey, folks. Sorry to disappear for the last couple of weeks.

Last weekend, I took the family to Atlanta, GA for a visit to the Georgia Aquarium and the Center for Puppetry Arts, both of which were fantastic (pics forthcoming). Unfortunately, amongst the souvenirs we brought home was the worst sickness my wife and I have had in years, which basically laid us both out until Thursday, and we’ve been recovering since.

On top of it, just before we left, I accidentally broke TwtStrm (my WIP TwtTxt reader), so I didn’t even have a functional way to keep up with the only “social media platform” I actually give a hoot about (nor a functional brain to try and fix it).

As of this morning, though, I’m happy to report that we’re basically all better, and TwtStrm is back to working. I’m actually hoping to get some code written this weekend (and maybe even try to get Parley running), but we’ll see how things go. 🙂

@movq@www.uninformativ.de Ah, I see. Didn’t cross my mind to use Inkscape for that. I hope to remember this once I run into a similar situation.

@david@daiwei.me @movq@www.uninformativ.de Yup, no issues. Only @bmallred@staystrong.run’s feed is broken for me for some time.

@itsericwoodward@itsericwoodward.com Then by all means, follow the instructions at https://git.mills.io/prologic/parley and setup your own instance on your own domain. It’s partly inspired by Twtxt/Yarn.social and Salty.im – in at least the way teh DNS discovery and WKID works. Once your instance is up and running and you’ve gone through the /setup and created yourself an account (or seti it up with an appropraite ODIC IDP) try something like /msg james@mills.io Hey! at which point you should automatically start peering with my instance. You should then be able to /join #lobby1 (a globally federated channel already across 2 instances so far). 🤞

@fossham@twtpub.com I honestly think the most unique and interesting thing about doing this at all is that it is in fact inspired directly by Twtxt / Yarn.social itself – That is to say, I am confident I can do this in such a way as to be “truly decentralised”, no inter-networking like ActivityPub, no centraised forges like Github or Codeberg. You run your instance, I run mine, we just are able to collaborate. Think exchanging patches over Email, just without all the hard-to-learn ways to do that (enough though it’s not hard for some of us, but still).

@movq@www.uninformativ.de @itsericwoodward@itsericwoodward.com Hahaha, a festival, indeed! :-D There was also “Raupenkrieg” (caterpillar war): jumping against each other in sleeping bags. I reckon that counts as pogo or mosh pit.

And back in the days, we had wonderful deep mud all around us, too! In extreme years we even needed to leave the camp ground for a day and walk to a gym with all the kids. There was just too much rain and the creek dangerously high.

We once had an actual creek running through the dining tent before the kids arrived. Luckily, it didn’t originate from the official creek, but the water came down the hillside. Unimaginable today with all these droughts in summer. Many creeks around here are dried up for several weeks, if not months now.

There you go, enjoy my favorite selection of yummy chocolate on the ground!

• https://wawuwo.de/old/wawuwo2006_woche2/montag/00020.html
  
• https://wawuwo.de/old/wawuwo2006_woche2/dienstag/00011.html
  
• https://wawuwo.de/old/wawuwo2006_woche2/dienstag/00018.html
  
• https://wawuwo.de/old/wawuwo2006_woche2/dienstag/00024.html
  
• https://wawuwo.de/old/wawuwo2006_woche2/freitag/00003.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/09.08.2007-donnerstag/00001.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/09.08.2007-donnerstag/00004.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/09.08.2007-donnerstag/00021.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/10.08.2007-freitag/00005.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/10.08.2007-freitag/00009.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/10.08.2007-freitag/00010.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/10.08.2007-freitag/00011.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/10.08.2007-freitag/00013.html
  
• https://wawuwo.de/old/wawuwo2007_woche2/11.08.2007-samstag/00001.html
  
• https://wawuwo.de/2009/woche2/freitag/043.html#image
  
• https://wawuwo.de/2010/woche2/abbau/016.html#image
  

It was a question of the mindset. Once we supervisors just made the best out of it and tried to had fun, the kids typically didn’t mind the mess either. Besides building huts, one of the most favorite things ever was actually “Matschschöpfen” (scooping mud). The kids scooped puddles into wheel barrows using giant soup ladles from the kitchen. “Sorry kids, time is up for today. Whoever sits in the closing circle first gets to go first tomorrow.” Unfortunatly, I don’t find any photos from that.

@prologic@twtxt.net Potentially, depending on the features supported / hardware used.

I’ve long wished for an appliance (like a video game console) that hosts my essential services - email, shared files, social media, etc. - but which “just runs” in a box behind the TV.

So what do you have in mind? 🤔

but yes, however you cannot currently add it or delete post via the app as I haven’t really built that feature at the moment you technically can do it, but you do run into some challenges with breaking threads if you’ve already published something and then go back and edit it so we generally advise not to do that too much if you can help it

@brytboi@twtpub.com I hope you’re seeing my replies because you absolutely can scroll up in the app. Let me know if you’ve run into a bug though and report it to me so I can fix it immediately!

@prologic@twtxt.net I only have one potential machine for this: My old netbook. I don’t want to accidentally brick it, though … 😅 It was scary enough to run my own OS on this.

@GabesArcade@gabesarcade.com I think it would have to be specific to the App itself. So say you somehow didn’t save a recovery key or some shit™ You could still get back up and running with ease if you had exported a config? 🤔

Dunno if anyone will find this interesting… But some ~6 months or so ago I experimented briefly with creating a whole bootloader + kernel + userland – Basically an entire OS in the Mu programming language (which as you know I also designed and created) – 6 months later I’ve worked on it some more after spending the last week working on improvements to Mu itself, which is now able to compile itself with its own Mu implemented compiler and now have an os/arch backend called muos/amd64 that boots into a running shell, with a tiny little vfs, UNIX-like semantics, syscalls, read/write, etc. It works pretty nicely, and aside from a small Assembly “nucleus”, most of the Kernel and Userspace is written in Mu.

https://git.mills.io/prologic/muos

I should really fix this damn bug where new replies to read replies to unknown conversation roots are not showing up in tt. I run into this bug almost daily for weeks now.

@prologic@twtxt.net I was actually trying to use twtxt.app, with Codeberg as a backend, but I kept getting a 403 error. As for twtd, well, my twtxt is hosted on a pubnix. The people behind Hashnix are really nice, but I’d rather not bother them with software requests if there’s a simpler solution, and I imagine it would be rude of me to run a deamon from my homedir without permission. Could be worth asking, though, unless I decide to write a client myself.

twtpub.com is just the default instance tho — it’s a multi-tenant twtd, AGPLv3. Run your own and I’ll list it in the app’s picker so folks choose where to land 🤗 keeps it decentralised + spreads the load. Docs → https://git.mills.io/yarnsocial/twtd

New in the Twtxt App 🥳 a Hosted feed backend — claim a nick, one tap, no account, no server, nothing to run. Your feed lives at https://twtpub.com/u/yournick and you’re posting from the app straight away 🎉

@balloonfu-sen@yarn.girlonthemoon.xyz Such tilde(s), etc, could in theory just run a twtd instance per user, or if I was convinced enough to make twtd also multi-user capable (optionally) that would also work. But many ~tilde(s) barely implement the Twtxt specs we continue to build and improve (albiet slowly and carefully).

@balloonfu-sen@yarn.girlonthemoon.xyz That should work. LMK if you run into any issues!

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/

@balloonfu-sen@yarn.girlonthemoon.xyz many reasons, all of which make sense. Same reason why automobiles today do not have an inner tube either. Now, about bicycles:

Tubeless bicycle tires drastically reduce punctures because internal liquid sealant instantly plugs small holes while you ride. Eliminating the inner tube also removes the risk of “pinch flats,” allowing you to safely run much lower tire pressures. This lower pressure provides superior traction and a noticeably smoother ride on rough surfaces. Finally, without an inner tube rubbing against the tire casing, rolling resistance drops, making your pedaling more efficient.

Bottom line, smoother ride, better traction, less flats.

@aelaraji@aelaraji.com oh, I totally understand. I also ran it too. I am running twtd as well. So, yeah, eating @prologic@twtxt.net dog food, foh sureh! 🤪

@prologic@twtxt.net I linked you some of my findings on the twtxt.app on IRC. The main problem is the hashing. Totally broken. But you have got to give it some thought, because GitHub hosting of the feed is tricky (even more so if they are CNAMEing their domain to it). It is also finicky because Pages is auto-enabled on username.github.io, so actions must run each time you twt.

Perhaps unsurprisingly, last night’s Magic games were dominated by the new Marvel set.

In game 1, I was running my new (unlisted) 5-color tribal Super Heroes deck (led by Nick Fury, Agent of SHIELD) against a lightly-modified Avengers Assemble deck, a tribal Super Villains deck (fronted by Thanos, the Mad Titan), and 2 “classic” magic decks (Fractals and Artifacts). The heroes held their own quite well, but that game went way too long (thanks to Thanos snapping away half the board every other turn). It finally ended when everyone quit after yet another board wipe (giving the wiper her first win).

Hey folks 👋 Today I announce the re-release of the Twtxt Search Engine now live and running and actively re-crawling and re-indexing. 🎉 Please report bugs or any useability issues to me! 🙏 #Twtxt #Search

Java 1.3 on Windows 95 with Proton as the editor could be another option for next Advent of Code.

Win95 runs pretty smoothly on my old box (no surprise, that box came with Win95) and I like Java, so … why not …

Not sure about the speed, though. 🥴

@lyse@lyse.isobeef.org This apparently depends on the program now … Some Qt6 programs still allow that, others don’t. I can’t remember if GTK ever had that feature. 🤔 But yeah, this whole “move stuff around as you please”-mentality is mostly gone.

I know I keep referring to StarOffice 3.1 a lot, but it’s just such a good example for all these things. All the toolbars and panels could be rearranged:

(This is running in Wine, btw.)

LibreOffice is the descendant of StarOffice and it doesn’t support anything like that anymore.

Maybe it was deemed too confusing for users? “Oh no, I mis-clicked something and now that bar is gone! How do I get it back? I don’t even know what it’s called!” 🤔

So I decided to change tact a bit with GoNIX and instead of trying to build apure Go browser from scratch (which I kinda of half succeeded, in at least it was able to render most static ssr sites), I’ve instead decided to write a new browsered using the Chromium Embedded Framework, otherwise known as CEF. So now I have a fully working browser in GoNIX 🎉 – However since my goal is to keep GoNIX pretty lcean and mostly written in Go, I delegated the cef part(s) to an OCI container image and run that with GoNIX’s box (command-line container runtime). It works great 👍

Interesting, HTTPS is almost twice as slow as plain HTTP on my server (~72 ms vs. ~135 ms):

$ hyperfine -r 50 "curl -so /dev/null 'http://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'"
Benchmark 1: curl -so /dev/null 'http://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'
  Time (mean ± σ):      72.7 ms ±  17.2 ms    [User: 6.2 ms, System: 4.8 ms]
  Range (min … max):    49.5 ms …  99.7 ms    50 runs

$ hyperfine -r 50 "curl -so /dev/null 'https://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'"
Benchmark 1: curl -so /dev/null 'https://movq.de/blog/postings/2024-05-23/0/t/word11a.jpg.jpg'
  Time (mean ± σ):     135.5 ms ±  28.9 ms    [User: 17.8 ms, System: 5.6 ms]
  Range (min … max):    93.2 ms … 198.5 ms    50 runs

Damn, I broke my Atom feed (and a reader let me know, that’s cool!).

I run vnu on all HTML and CSS files after each build of the website, but I don’t run a feed validator. 😬 Time to change that.

@lyse@lyse.isobeef.org You think I thought about it on that level? 😅 I just heard that weird animal noise in the dark and I was the one who was running. 😂

@movq@www.uninformativ.de But foxes always run away and don’t attack. They’re afraid of us humans – unless they have rabies.

@balloonfu-sen@yarn.girlonthemoon.xyz Oh! You’re running Yarn.social’s yarnd? 😅 That’s why I was able to see your reply so quickly/easily ! Nice! And welcome! 🙏

@movq@www.uninformativ.de

What’s your motivation for running this, btw? 🤔

Basically, two things a) feeling generous for folks that either can’t afford or find it hard to have a little place to call home (webpage, feed, whatever) and b) a real opportunity to test some of the components that make it possible sshbox, which I know works well as it fronts my Gitea instance’s Git+SSH service and box, a container runtime I wrote a while ago, recently improved, hardened and polished.

@lyse@lyse.isobeef.org Okay, wait, what is the anti-feature here? The nag screen because it’s “old”? The inability to update when run from source? 🤔

@prologic@twtxt.net I think I said this before: This looks like a really cool thing! I just wish I had a use case for it, then I’d be all over you. 😅 But since I run so many servers of my own already …

What’s your motivation for running this, btw? 🤔

Oh come on! Why such a stupid anti-feature!?

WARNING: Your yt-dlp version (2026.03.17) is older than 90 days!

     It is strongly recommended to always use the latest version.
     You cannot update when running from source code; Use git to pull the latest changes.
     To suppress this warning, add --no-update to your command/config.

@movq@www.uninformativ.de That’s right, way harder than centrally managed. They even didn’t reach concensus over the main folder: “Alle Programme, “Alle Programme (x86)”, “All Programs”, “All Programmes”, etc. Anyway.

For class 11 (or maybe already in 10, I don’t remember exactly) we could choose either between traditional maths class with a graphical calculator or “Mathe mit CAS”. There were two teachers in my entire school who were able to teach the latter. It was also fairly new at the time I believe. Certainly unheard of for a „allgemeinbildendes Gymnasium“, maybe the technical ones were already offering it for some time, not sure. It was clear to me that I would take the maths with CAS class.

Each kid had to buy their own Cassiopeia A-Something. I don’t know how much that thing was (definitely more expensive than a graphical calculator) and whether the school subsidized that in any form. But it was slow and underpowered as hell. We rarely used it in class nor for homework (most if not all had already a desktop at home). Typically, when we worked with the CAS, we sat down on the desktop computers. Our class took place in one of the two computer rooms. The desktops were placed on the three sides (left, right, back, facing the walls or windows) and the regular school desks were in the middle. Since there were more pupils than desktops, we always shared. Nowadays, we call it pair programming. ;-)

For the exams we had the “mandatory part” (Pflichtteil) without any tools. Once we finished that and handed the papers to our teacher, we were then allowed to boot up our Cassiopeias and work with them for the second part. Before the exam started, everyone had to show the teacher that they reset their small computer to factory settings. This second part was called „Wahlteil“. But you had to do it in order to pass. So, I never understood the choice of this term. Maybe it’s because the first part is the exact same for everyone (graphical calculator and CAS class), but the second part was definitely different for the two classes. Each suited to their tools.

After one or two exams, it became clear that the Cassiopeia was far from ideal. So, we took the second part at the desktop computers from then on. Our teacher unplugged the network cables himself to avoid cheating. Each computer had an “HDD Sheriff” running that reset the disk at startup. There was also an issue that the personal user accounts were affected by that. Sometimes all your data were lost. If you were lucky, they were still there. So, we saved our Maple project to local disk (if the computer didn’t crash in between, that was no problem) and at least eventually before leaving the classroom, we then also saved it on the server. For that, the teacher quickly plugged in the cable, we saved, and then the cable was unplugged again immediately. Oh, and everybody used their USB sticks, too.

All in all, this Cassiopeia A-* was quite a useless purchase. :-D I’m not sure if I still have it. At least I thought several times about giving it to the flea market. Don’t know if I did or not.

Some activity at the lake, so I couldn’t do my run there. Came home and jumped rope for 81 minutes! I wil be sore tomorrow, but it was worth it.

There was an event being held at the lake, so I couldn’t do my run there. Came home and jumped rope for 81 minutes! I wil be sore tomorrow, but it was worth it.

After the last two days were dry and a tad warmer, I left the house a few minutes later to check again. It was similar to last time. One deer on the pasture that didn’t run off, it was roughly 15-20 meters away, a bit further than the day before yesterday. Probably even the same individual. Many moths, zero fireflies and another two deer on the mown meadow when I left the forest. Those were closer to 50 and 100 meters away and evenutally escaped into the woods. The same street lamps were off, too.

The lovely smell of cut grass was in the air. Venus and Jupiter reflected brightly in the West. What a stroll, I call that a great success. :-)

I went to check on the fireflies this season. But I didn’t see any. Instead lots of moths. At first, I thought it might have been still too light, but it was already dark enough for me to miss and destroy a snail shell. Bummer. Maybe it was too wet tonight. Although, it’s probably just another or two weeks until my glowing friends will finally show up.

In the beginning, I passed two beautiful deer on the edge of the forest. They were just ten meters away, but didn’t run off, really cool. :-) I kept on walking. Before I eventually left the woodland, a frog or toad crossed my path. It was very dark by then, though, so all I could see was a black blob.

Back in town, the street lamps on the first third were all turned off for some reason. I was already glad that I will reach home without getting blinded this time, but unfortunately, the other lamps were all operational.

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

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

On the subject of debugging these so-called AI(s) / Black Boxes… the model is a black box sure, but that’s not really the problem. Everything around it — the inputs, the outputs, the decisions it makes — all of that can and should be fully logged, traced and replayed. The “program” isn’t the model, it’s the full context you feed it. That’s what you debug. It’s not so different from any other system really; if you’re running something in production with no logs, no structured outputs and no tests, you’d have the same problem. The model doesn’t change that discipline, it just makes it more important.

@lyse@lyse.isobeef.org @tftp@tilde.town Someone has pointed out that there’s OpenRsync:

https://www.openrsync.org/

Since I run OpenBSD on my servers, I actually do use that and have never noticed any incompatibilities with the “normal” rsync.

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