Personally my arch install is almost boring me with how stable it’s been - and if anything goes wrong, it backs itself up before and after every single update plus on every boot just cuz, so I can roll back to wherever I want. I’ve put a lotta work into building out all these redundancies I’m happy with, and arch has been so goddamn stable I haven’t even had an excuse to use them. The process of getting a complete install was absolutely not “it works” - but now that I’m there, yeah, it really does just work. My only complaint is that I don’t have any reason to tinker with it more.

It physically hurts me to say anything in facebook’s defence, but to be fair this is an account centre link to an account config page

I didn’t consider account recovery, that’s a good point. Personally I don’t usually bother with it for anything I want to be private - if I lose it I lose it lol.
It’s still not perfect, but some of the private email hosting providers like proton have email aliases, so you could use one for recovery without giving any info to hackers (assuming you trust the email provider). Definitely less secure than only a public key being exposed, but maybe an acceptable tradeoff for the convenience of an existing established solution?

You rule out social networks, but why? Wouldn’t a fediverse microblogging (or full blogging) platform work fine for the purpose? Just pick an irrelevant username and a strong+unique password and only access your account through tor using any and all relevant best practices.
Given you want the continuity of the author preserved, I don’t see the functional difference between the posts being associated with an anonymous account and them all having your public key. Am I missing something?

Honestly I’ve found the opposite of what you said, where on Debian based distros I commonly had to go to a project’s git repo and follow readme instructions to build when it wasn’t in an apt repository. Meanwhile on arch, the only thing you have to install manually is yay and then afterwards everything is in the AUR. Not saying that makes arch more user friendly than Debian (obviously), but that one aspect I do actually find easier on arch at least if you’re willing to use an AUR helper.

I don’t think I’d call it anything wrong, but the subvolumes definitely do make it different for installation purposes so that following ext4 instructions for bootloader configs or kernel arguments could put you on the wrong path

Some desktop environments (plasma 6 at least) support it when running in Wayland - my daily driver for months has been an HDR setup (with a nvidia gpu, even) and it’s been great. It’s not quite ready for non-technical users, but imo it’s not far off and I can’t wait for it to be more common.

To put this into context, the zen5 X3D chips aren’t out yet so this isn’t really an apples to apples comparison between generations. Also, zen5 was heavily optimized for efficiency rather than speed - they’re only like 5% faster than zen4 (X series, not X3D ofc) last I saw but they do that at the zen3 TDPs, which is crazy impressive. I’m not disagreeing with you about the 7800X3D - I love that chip, it’s def a good one - just don’t want people to get the wrong idea about zen5.

Yea as opposed to the windows method of “just open regedit and navigate 8 folders below HKEY_CURRENT_USER to change some ambiguous system variable in hex” lmao

I’ll take editing a text file in /etc/ for my configuration any day

Never thought I’d have to give the Texas government credit for anything tbh, but I’m glad to be wrong. Now if they wanna keep this momentum going and repeal all the awful dehumanizing laws they’ve passed recently, maybe I’d even start to respect them lmao

Yes but like it or not, it’s a threeway with zuck

I remember being able to figure out a solution with the kwin docs and dfeet for introspection, but it was a while ago and my memory is less than stellar lol. I ended up running all my window-related logic in the kwin script (js) and just using python+dbus to see if the script had been injected and do it if not. If you go the same route (though the python is unnecessary this way if you aren’t using it for something else, like running one of the windows you wanna manipulate) the workspace global variable stores all windows in stackingOrder, so looping through that list (for (window of workspace.stackingOrder) {…}) is an easy way to check each window. I definitely remember docs on the workspace/windows part, but tbh I think I just introspected with the jsconsole.log and the log kwin prints it to (journalctl maybe?). Sorry I don’t remember more about the process, I got into the kwin scripting for all of an hour cuz of the Wayland regression of not being able to control your own window’s size/position in qt so it was a bit of a hack fix I haven’t had to think about since.

I’ve had good luck interfacing with KDE windows using dbus in python, although if I remember right the more granular control also required javascript (still passed thru dbus with python). The only python library I needed was Qt (for their dbus implementation because I was already using their event loop, but any other lightweight dbus package should work fine).

In Canada we have Kijiji, which is… not perfect for privacy, but at least it’s not facebook