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