The real challenge facing a kremlin linux fork isn’t opposition, it’s deciding what to do once they realize there aren’t any maternity wards in the kernel they can shoot ballistic missiles at.

Forgejo, a Gitea fork used by Codeberg. I chose it because it’s got the right balance of features to weight for my small use case, it has FOSS spirit, and it’s got a lovely package maintainer for FreeBSD that makes deployment and maintenance easy peasy (thanks Stefan <3).

RIP

DNS is what you’re looking for. To keep it simple and in one place (your adguard instance), you can add local dns entries under Filters > DNS Rewrites in the format below:

192.xxx.x.47 plex.yourdomain.xyz
192.xxx.x.53 snapdrop.yourdomain.xyz

What is your root filesystem installed on - lvm, zfs, or bare disk partitions? Are you booting with grub (legacy/bios) or systemd-boot (uefi)?

Without an argument, the -j option will start jobs with no limits - depending on the project, this could be thousands or tens of thousands of processes at once. The kernel will do its best to manage this, but when your interface is competing for cpu resources with 10,000 other cpu-intensive processes, it will appear frozen.

Make’s -j option specifies the number of concurrent jobs to run, and without an argument doesn’t limit that number at all. Usually you pass an argument to it with the number of cpu cores you want to utilize. Going over the number of cores you have available (like it does without an argument) will be slower or even freeze your system with all the context switching it has to do.

In the bridge-vids option, you can replace 2-4094 with a space-separated list of vlans to be allowed tagged ingress/egress on the bridge interface, if you prefer to limit it. Nothing in the GUI for that, as far as I know.

ssh predates the specification, exists somewhat independently of even the idea of a desktop (not common to see xdg env variables like XDG_CONFIG in a headless environment, for example), and uses the homedir/.ssh directory on both the client and server side of a connection. I think it’s less to do with security and more to do with uniformity for something as important as ssh - ssh doesn’t need to change to use the xdg spec, and xdg doesn’t need to allot anything special for ssh when it’s already uniform across the unix spectrum

If you aren’t going to fully wipe your drive in horrible events like this, at the very least use shred instead of rm. rm simply removes references to the file in the filesystem, leaving the data behind on the disk until other data happens to be written there.

Do not ever allow data like that to exist on your machines. The law doesn’t care how it got there.

If you can find a cheap used micro-form-factor pc with hdmi output (eg thinkcentre m93p), that’s a great sustainable way to go. Stick debian on it, get a cheap tiny bluetooth keyboard/trackpad, stream via web browser. Bonus if it’s got a dvd player, for the ultimate utilitarian foss htpc.

For donating compute/storage/bandwidth to community archiving, this is a great place to check out: https://wiki.archiveteam.org/

Just my opinion, but I think they’re a great project to support.