Your ability to ride the fence is admirable OP, don’t let anyone take it from you 🙏

Nah I ain’t about that rust life

cgi on the other hand… 😍😍😍

It’s as easy as following any set of instructions. Whether or not you actually understand what the instructions are doing is an entirely different story. If you actually want to learn how to operate a posix system, doing a bunch of command line installs of Linux isn’t going to help you with that. What will help is living in something with excellent documentation like OpenBSD, with minimal reliance on external tooling. Once you have the skills, they’ll transfer anywhere.

Or even better, write userscripts that can be used anywhere instead of inside some non portable extensions framework

If you’re going to give GNOME shit, at least let it before how much they destroy portability of GTK, enabling cancer like Client Side Decorations, and ignoring their community when it comes to things like desktop icons.

Russian/Chinese software contains spyware: 😡😡👿👿💢💢

US software contains spyware: 😇👉👈

For destructive commands I much prefer find / -type f -exec mv {} /blackhole \;

Friends don’t let friends use IBM software.

thanks for the brain rot, op 🙏

lmao how much did steve ballmer pay you to write this

Just make the file root owned and readable by no one. An unreadable file can’t be copied. You can use chattr to add some flags like immutability if you desire (shouldn’t really need to). Use a command like find /some/path -type f -exec chattr whatever {} \; if you need to do this recursively. Root account should need a password, and should (hopefully) not be accessable with an unprivileged user’s password through sudo/doas, but on its own account with it’s own password using su or login.

Note that without encrypting the file, this does not protect you from someone just grabbing your storage device and mounting it with root permissions and then they can do whatever they want with your data. It also doesn’t protect you if someone gets root access to your device through other remote means. If you want to encrypt the file, use something like openssl some-cipher -k 'your password' -in file -out file.cipher_ext. If you want to encrypt multiple files, put them in a tarball and encrypt the tarball. You can again also use find with openssl to encrypt/decrypt recursively if you don’t want to use a tarball, which may be better with ciphers like blowfish that aren’t secure at large file sizes; but if you do that, you expose your encrypted file system structure to attackers.

I am not a fan of full disk encryption, because it usually means leaving all your data decrypted during runtime with how most people use it. If you only decrypt a block device when you need to, there’s nothing wrong with that, and can work as an alternative to encrypting a tarball.

Telemetry you can’t easily disable (requires modifying about:config, can change on update), Glean (nastier than anything in chrome), DoH to cloudflare, pocket (adware), Anonym.

https://www.jwz.org/blog/2024/06/mozillas-original-sin/ mozilla “saving the web”. If you want to save the web, use something like qutebrowser, luakit, or falkon with drm compiled out.

https://www.jwz.org/blog/2024/06/mozilla-is-an-advertising-company-now/

Chrome being worse than Firefox doesn’t make Firefox’s default telemetry, adware, and DoH to cloudflare good. When the bar is Chrome, essentially any browser passes.

Users should be afraid of the malware that is default firefox. Why do you think so many people use forks?

Flatpak’s usecase for me is Alpine Linux and other distributions that use musl or other libc implementations. I don’t love it, I think its cli interface and the way you add flatpak servers to be obtuse and annoying, but it is useful for getting glibc dependent software.

OpenBSD’s default public domain kornshell fork on OpenBSD, oksh (portable OpenBSD ksh clone) on Linux/MacOS/Other Unix. It has far fewer extensions than something like Bash (which I consider a positive) while being much faster (tested with hyperfine), and the extensions it does have are all useful (arrays, coprocesses, select, .* not expanding to . or .., pattern blocks, suspending of the whole shell).

I dislike the paradigm that there are “techy people/programmers” and “tech illiterates/non programmers”. Anyone can develop the skills to properly use unix interfaces given proper training; and I know that’s true because the whole world used to run (mostly) unix on the desktop before corporate took over. Unix doesn’t need to be windowsified/macosified to get people to move over; people need to unlearn the interfaces corporate has brainwashed them with for generations. There are so many more interesting user interfaces than just what Windows and MacOS provide; graphical or otherwise.

Except the gold is actually poop and the shovels require burning several trees per dig

A time for celebration

wonder what fraction of a fraction of a percent of their yearly profit they’ll be charged this time