How much sandboxing is your distro generally doing?
rotopenguin
joined 2 years ago
I just typed "xdg-download:𝗰𝗿𝗲𝗮𝘁𝗲" into flatseal, my browser is safe af now.
From Dr Seuss's "The tough coughs as he ploughs the dough"
Fish for an interactive shell, and I'll often drop back to bash for writing a script. I can never remember how to do basic program flow in fish. Bash scripting is not great, but you can always find an example to remind you of how it goes.
Aww, c'mon. It's never too late to be isekai'd into a a fantasy universe where you are the central love interest. That's my plan/only realistic possibility, anyway.
The large /var suggests flatpak, and that plays some hardlinking games.
(If you ever need to free up / space, shifting your flatpak usage to a --user repo will help a lot. No there is no handy command for that, it's a matter of adding and deleting one package at a time.)
Btrfs subvolume create /.nodelete
That way, "btrfs sub del" cannot hit your root subvolume without you first removing .nodelete .
If you set up flatpak as --user, bringing your home directory over would be 99% of the job.
It's a lot to toggle off, on each computer, multiplied by every other computer that you're connecting to. It's too insecure-by-default.
Does it support "sending a file larger than 2 gigs, without mysteriously deleting it at the end, but if you manage to sneak a hardlink to the file while it's transferring then it's okay"?
KDE connect is a large suite of some good, some half-baked, and some just plain scary remote tools.
I'm liking LocalSend for the occasional "I want some files/pictures/text to go from here to there".
If you don't want files to be accessible by you, then have another user own them.
If you don't want files to be accessible by root, then don't have them at all.