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