This is going to take a while … See ya in a couple of days/weeks.

I have a day off, national holiday.

What happened so far:

• Internet outage since early in the morning. Still going on.
  
• Unable to reach a human being at my ISP, so I hope they mean it when the computer voice says “we know it, we’re on it”. 🤣
  
• systemd (PID 1) crashed. Might be partially my fault, but meh.
  

I take this as a sign to not do any computer stuff today. 🤣

@prologic@twtxt.net Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂

Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)

@mckinley@twtxt.net It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)

I need to optimize this. 🥴

The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.

Now that I think about it … I only remember one PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in software, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.

So … my little NAS probably won’t die any time soon. Hmmm.

@mckinley@twtxt.net Not really sure, to be honest. Probably a couple hundred GB … ? 🤔 With the changed data, it might be half a TB to transfer? I’m just guessing.

Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)

I think the solution is to have less data. 😈

@lyse@lyse.isobeef.org Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤

@prologic@twtxt.net From the DOM? That can’t be right. 😳😳😳

@prologic@twtxt.net It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did not get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. 😅

@prologic@twtxt.net Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔

@prologic@twtxt.net Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)

@prologic@twtxt.net My client tells me when it fetches archived feeds. That’s all.

@prologic@twtxt.net Ah, yes, that’s better! 👍

(Hmmm, I think I could add the time of the last twt to the output of jenny -l. 🤔 Currently it only shows the last successful retrieval time.)

@prologic@twtxt.net Every now and then, I get a notification about Yarn feeds getting archived/rotated. 😅 Appears to work without issues. 👍

@prologic@twtxt.net One minor detail: The Makefile wants to run date -Is, which doesn’t exist on OpenBSD. Not sure how relevant this platform is for you, though. 😅

I haven’t come up with a portable solution yet. date '+%FT%T%z' is the closest approximation that works on both GNU and OpenBSD, but it doesn’t include a colon in the time zone offset, so it’s 0200 instead of 02:00. 🤦 I’m not sure if this is ISO8601 compliant. And it’s still not POSIX. 🤦 Well, I tried. 😂

@prologic@twtxt.net Newcomers might have a little difficulty because just “installing” a Go compiler is not enough – you also need to add ~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:

openbsd$ gmake server
/bin/sh: minify: not found
/bin/sh: minify: not found
/bin/sh: minify: not found
gmake: *** [Makefile:84: generate] Error 127

Maybe extend Yarn’s guide just a little bit, like: “… be sure to have Go installed and set up properly, e.g. env vars are set …”? Maybe that could point readers into the right direction. 🤔

What I don’t like about my strategy is that it’s so slow. ☹️ I did change a lot of data this time, so it’s slower than usual, but still …

The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)

The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.

Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still working, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.

@prologic@twtxt.net I just set up a Yarn instance from scratch and, honestly, I don’t think a yarnd setup is needed. 🤔

I followed the instructions here and they were simple enough: https://git.mills.io/yarnsocial/yarn/src/branch/main/README.md#configuring-your-pod

It needs a little polishing (for example, it says COOKIE_SECRET is optional which it isn’t), but it was a good experience overall.

Maybe it’s just me, but I prefer reading installation instructions. And I believe that not having something like yarnd setup nudges you (the author) into keeping those instructions short and concise. Whereas the existence of yarnd setup means that you can cram everything and the kitchen sink in there, because it’s convenient. That can lead to a convoluted setup process – and me, the user, does not really know what that command really does, which is something that I, personally, don’t like. 😅

I wonder what Android does now that I’ve blocked all those connections. Will it queue all the data and just send it the next time it has an internet connection (which will happen sooner or later)? That would mean my blocking attempts are mostly pointless. 🥴

No way of telling what’s going on, it’s all encrypted …

@prologic@twtxt.net Get fucked, indeed. 🫤

@prologic@twtxt.net

things we don’t even know about or have any control over (or very little)

That’s the thing: It’s not apps doing weird stuff, it’s the phone’s operating system itself. I can choose which apps to run and which permissions they have, that’s all fine, but what the fuck is “ImsApp” and why does it need access to GPS and my camera?! Completely untrustworthy.

Experiment: Locking down my Android phone in the firewall, only allowing outgoing connections that I approve of. Let’s see how that goes.

Even just looking at the log of attempted connections is scary. This thing is talking to everything all the time. Worse, there are some system apps that regularly query the device’s GPS location and you can’t turn that off … Shitty spy device. 🙄

@prologic@twtxt.net Noticed any slowdowns? I noticed a ~0.2 second delay when opening new shells, never bothered to check it, and now found out that it’s caused by the ~250k lines of shell history. 🥴

@lyse@lyse.isobeef.org You mean you edit this file manually sometimes? 🤔

@mckinley@twtxt.net Wow. And you never wonder: “Wait, how did I do $thing back then?” Happens to me all the time. 😳

@bender@twtxt.net My condolences. 😂🙉

@bender@twtxt.net Ah, so that’s the plane with the Brazilian women then. 😅 Enjoy your stay!

@bender@twtxt.net To infinity and beyond? 🤔 How large is it currently? history | wc -l

QOTD: How large is your shell history? No history, 500 lines, 10’000, 100’000, something else?

@prologic@twtxt.net Oh, so the cache just goes back about a month? 🤔

@prologic@twtxt.net Lol, god no 🤣

Well, I missed the time window. Time flies, they’re all grown up now. 😬

One great feature of Vim (and probably other editors) is “keyword completion”: Type the beginning of a word, then press Ctrl-N and Vim will give autocompletion options by scanning all the words in the current file. For example, when I now type “au” and then Ctrl-N, it will suggest “autocompletion”.

This is so very useful when writing text / prose. It’s especially useful for German text with all those long words like “Informationssicherheitsbeauftrager”. I use this feature all time and I sorely miss it when I’m forced to use some other crappy editor. 😩

https://movq.de/v/96049c4aea/s.png

Those options are now included in jenny’s Vim package:

https://www.uninformativ.de/git/jenny/commit/698c4382208c5b5eb87999a30fd657167ab5b694.html

@lyse@lyse.isobeef.org Awwwwww! 😍

@aelaraji@aelaraji.com You’re welcome. I guess this could/should also be mentioned in jenny’s docs. 😅

@aelaraji@aelaraji.com That’s the trick, yep. 👍 I have something like this in my .vimrc:

au BufRead,BufNewFile jenny-posting.eml setl fo-=t wrap

(That hard disk was in a Windows box and there was no such thing as RAID or anything similar. Didn’t have the money for fancy stuff anyway.)

@mckinley@twtxt.net Yes, over 20 years ago, a hard disk died. Not completely, only some parts of it, but it was enough to destroy ~30 GB or something like that.

I bought a lot of DVDs over time and many of them have become unreadable. Star Trek DS9 is among the victims, parts of TNG, parts of X-Files. Really annoying. I didn’t have the required disk space to make backups and, honestly, didn’t think they would die so quickly. When/if I buy movies these days, I either make a backup right away or I treat those DVDs as “will die soon”. 🫤

CDs regularly die, too, although not as often as DVDs.

And of course, lots of floppy disks are dead now. 😂🫤

@bender@twtxt.net Yep, it’s pass. 👍

YouTube introduces a “stable volume” feature:

https://movq.de/v/ad0dd48aac/a.jpg

Once filmmakers realize that people just want stable volume instead of SUPER LOUD SECTIONS (…andreallyquietones…), then maybe I can finally remove the limiter from my pipewire filter chain. 🥴

In case you need a profile picture: https://thispersondoesnotexist.com/

@aelaraji@aelaraji.com Why not, give it a shot! 😅

I think I even integrated my password manager into tmux at some point. There’s a lot that you can do.

@lyse@lyse.isobeef.org Same here. I’m watching the storm tracking on kachelmannwetter.com 🍿

@aelaraji@aelaraji.com Ah, right, you were only talking about 24 hours. I think I can manage without Netflix for a day. 😅

@aelaraji@aelaraji.com At work? Not a chance. 😂

Private life? Sure. There was a regular community event called “A week in the TTY” over at nixers.net, where we spent a week only in text mode. It was easily doable.

There are some things where a graphical browser is pretty much mandatory these days. Online banking comes to mind. I could in theory physically go to the bank, but I’m way too lazy for that. 😂

Netflix is more popular nowadays and I wouldn’t want to miss that, either.

@sorenpeter@darch.dk Not bad, maybe let’s go back to 98.css. 😃

@bender@twtxt.net It feels like the current cycle has been going on for a very long time now, almost 20 years. 😩 But I might be wrong here, maybe it started later.

Is this “flat UI” madness ever going to end? I’m beginning to lose hope.