Honestly i can defend many americans not having interest in geopolitics but yeah those guys were astonshingly ignorant 😂

I try to follow a multi-factor, multi-domain model.

So if I am wanting to verify that data is on the system I except it to be then TPM keys and measured boot is what I use. To verify it is on the network I expect I use a Tang server. To verify I have possession of a device I use, a hardware token and password.

You could do all the above, or mix match depending on the system. For example for servers I assume they need to boot without user intervention, so password is set as backup to the Tang server. I still use hardware token to buy just for quick revoktion of verification (i.e. I know a server is compromised or could be soon, I can just pull a USB out).

The same setup works for my laptops, which makes my network because of Tang act as trusted domain as well.

So again multi-factor (something you have, know, are, do) and multi-domain (network, user, machine).

I use Clevis to do the multi-key unlocks.

I actually saw this being used before I knew GitHub had one. Seemed reliable to me!

Dockers permission structure AND service running as root really does baffled the mind sometimes

Gentle reminder that there, in fact, much better ways to deploy containers.

There are cases of but also on going programs.

Their building a Prison System ™️ regardless, open source (e.g. Linux) just offers SOME protections.

We have to do more regardless, but it’s still all part of the good fight in my book

How have tests gone so far?

also cool concept, you can actually get eBPF XDP to compile to FPGA on some smart NICs even further pushing it away from the core system if it works!

No problem!

That is a runtime that some flatpaks use as well.

Gnome and KDE as projects are a bunch of things, from login managers, to compositers, desktop UIs, and user application (like Gnome “System Monitor” or KDEs “Plasma System Monitor”).

You can actually mix and match some pieces and they just work, but especially the user apps because both teams put in work for interoperabilty or Freedesktop standarization.

So you can have an app that uses KDEs shared libs and an app that uses the Gnome projects libs on the same issue with rarely any issue. Even more so with flatpak since the all of the files those apps see are in what is called an overlay filesystem, so your kde apps get a layer of files jist for KDE apps to build off of and gnome apps get a layer of files just for them to use. In flatpak these are called runtimes. That is what is being updated here.

Tbh everything that makes those systems good for noobs works on other systems. Flatpak, distrobox, homebrew and btrfs snapshots.

The immutable OS part is actually just optional lol

Non-sequitor because people will blame the dumbest stuff on stuff they think is “wierd”

“Lets fight ICE” also “you need an id to use your laptop and be verifed by big tech to use it” Worse then clowns. Fucking traitors

[email protected] Called it “immasculate conception” and i just fits too eerly well for me to forget

I track AirTags with the android AirGuard app. It might be able to do more maybe?

People are wild. Its just like locks on doors. Yes very useful, the user should have the keys, yeah corperate ownership of keys is nightmare.

The nice thing is you can give a container full hardware access if you wanted too. So if perf was a must, just steal the whole GPU for the container.

Though my ideal would be sidecar container to base desktop container. Just share what you need bus, and device wise.

Build tool, package builder, package manager, configuration manager, and a distro built on those aspects. You can use any aspect indepently though

2026 I will continue to use the Linux Desktop. My current prediction and I’m sticking to it

https://matrix.org/ecosystem/bridges/

Services that link matrix servers to other chat services.

https://gitdab.com/cadence/out-of-your-element

Currently.