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

@lyse@lyse.isobeef.org Nice!

@prologic@twtxt.net Happy belated birthday to you, sir! 🎂

@david@daiwei.me Right? I loved seeing it on the big screen. It was even the Director’s / European cut, with the little Nazi-killing bit in the middle. “It’s a kind of magic!” ⚔️

@lyse@lyse.isobeef.org Yeah, it’s what we use for streaming. We’ve had a YouTube Faamily plan for years (we originally signed up to keep the ads away from the younglings), and it’s included as part of the deal. I also have some hard-to-find music I uploaded to it back when it was Google Play Music. Still, I wouldn’t recommend it to anyone, per se.

@klaxzy@klaxzy.net Absolutely! “Angel Dust” was (and still is) my absolute favorite album of all time, from any band. It is (and remains) that damn good. 🤘

@lyse@lyse.isobeef.org Added to the calendar, thanks!

@prologic@twtxt.net @david@daiwei.me Good to know! 😃 I’ll let y’all know if I get stuck.

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 Oh yeah, very interesting. Thanks for telling us!

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

🎶 “Regina” - The Sugarcubes https://music.youtube.com/watch?v=QpEz9pfJS7g&si=lKj-diIWGoi5BrWJ

@movq@www.uninformativ.de Yeah, some letters are really unreadable. And I always, always read the “s” as an “f”. Every time.

Yeah, I find it telling when Nazis use Fraktur. Very interesting, I wasn’t aware that occupied regions couldn’t read the orders.

That was an interesting read about C:

https://pikuma.com/blog/c-integer-sizes-not-a-mistake

@lyse@lyse.isobeef.org Might be because the typical “German Fraktur” (this isn’t a thing) uses very unusual uppercase letters. And “k” is just weird. And “f” and “ſ” (long “s”) are very close together.

This is “Luther’sche Fraktur” from around 1708 (a photo from the book “Fraktur” by Albert Kapr), the book says this was one of the most popular ones:

I have lots of trouble deciphering those uppercase letters.

By the way, this is worth mentioning: Fraktur fonts are often associated with Nazi Germany, but did you know that the Nazis eventually banned these fonts in 1941?

Yeah. Typical Nazi stuff.

@lyse@lyse.isobeef.org Coloring wasn’t too bad, I did it in Inkscape where I can easily move those rectangles around. 😅

@movq@www.uninformativ.de That’s dedication. And it really shows. Again, your font is easier to read for me than the average Fraktur I come across. I don’t really understand it, but I trip more often in books.

@movq@www.uninformativ.de One more human to add, I just got to read it. Cool stuff, coloring in these hexdumps by hand must have been a ton of work, my goodness. Much appreciated, though. :-)

Oh, and only 29 clients have requested the actual image:

29 movq.de/blog/postings/2026-09-25/0/bine-initial.png

Assuming that that’s an actual human being who’s interested in the content, then it’d be less than 1% of the hits that I get.

I’d estimate that ~90% of the traffic I get is some kind of non-human / non-browser thing.

Here are some numbers on the recent blog post:

3804 movq.de/blog/postings/2026-09-25/0/POSTING-en.html
 404 movq.de/blog/postings/2026-09-25/0/t/bine-initial.png.jpg

The HTML page is obviously the blog post itself. The image is the thumbnail of the “opener” image: That’s the thing that you’re pretty much guaranteed to see when you open the post in a browser.

But out of the 3800 hits on the HTML page, only 400 (~10%) are also requesting that image.

So … it’s ~90% noise, right?

@lyse@lyse.isobeef.org Thanks. 😅 I didn’t check the time, but I guess something between 15 and 30 minutes? 🤔