Bitwarden. Hands down the best decision I made in regards to web safety was switching to a proper password manager.

Close second is uBlock Origin.

Also make sure to use DecentralEyes for easy enhanced privacy.

I use NoScript, but that level of granular control isn't everyone's cup of tea

My ideal form of government is one where everyone cooperates to build up society, and there may be leaders, but no one is owed obedience.

nope. Especially now after having lived for a few years in a booming rehab community, seeing secondhand where addiction gets people.

I did coke a few times, it was okay. The high doesn't last long enough to justify the cost, and I was already jonesing for more the last time

I have a tinkering laptop set up with Fedora, DNF is as simple as APT and friendlier imo. I've switched to Nala (an APT wrapper that enables concurrent downloads) on my Debian PCs. YMMV.

Simply put: every distro needs its own package manager because the distros handle packages differently, from the way software is bundled and distributed, to where files reside in the filesystem.

E.g. APT is so friendly because of how rigid Debian is about the structure and info that is bundled within the .deb archive, which Pacman users tend to consider as unnecessarily restrictive bloat that impairs download/installation times. Meanwhile, yay (and other AUR helper programs) compiles the packages from source.

Although there are some that work across distros, like Nix or Homebrew. Plus there's always flatpak or AppImages or (shudder) Snaps.

And of course, if you want people to think you're basically a programmer, there's always

$ git clone <git repository>
$ cd <git repository>
$ sudo make install

(for software that is packaged with a Makefile)

Looks like for speed EXT4 still reigns, but that misses the point of ZFS, Btrfs, Bcachefs AND F2FS, which are all COW filesystems and not intended to outperform journaling filesystems in speed.

Another program that works on Windows, which I prefer to Balena Etcher, but less so than Rufus: unetbootin

Even the manpage Telorand linked mentions it by name for non-interactive use.

Also, make sure you use the right program depending on thr partition table : sgdisk is the right choice for GPT disks, sfdisk is for MBR.

Use conv=fsync

This ensures the cache is written before dd exits, but doesn't necessarily write to disk directly. This means that, for small files, dd can finish release its hold on the input file quicker

iw dev <interface> station dump will show every metric about the connection, including the signal strength and average signal strength.

It won't show it as an ascii graphic as with nmcli, but it shouldn't be hard to create a wrapper script to grep that info and convert it to a simplified output if you're willing to put in the effort of understanding the dBm numbers.

E.g. -10 dBm is the maximum possible and -100 dBm is the minimum (for the 802.11 spec), but the scale is logarithmic so -90 dBm is 10x stronger than the absolute minimum needed for connectivity, and I can only get ~-20 dBm with my laptop touching the AP.

Basically my point is that the good ol' "bars" method of demonstrating connection strength was arbitrarily decided and isn't closely tied to connection quality. This way you get to decide what numbers you want to equate to a 100% connection.

I'm a big fan of the idea of efficient computing, and I think we'd see more power savings at the End Users based on hardware. I don't need an intel i9-nteen50 and a Geforce 4090 to mindlessly ingest videos or browse lemmy. In fact, I could get away with that using less power than my phone uses; we really should move to the ARM model of low power cores suitable for most tasks and performance cores that only turn on when necessary. Pair that with less bloatware and you're getting maximum performance per instruction run.

SoCs also have the benefit of power efficient GPU and memory, while standardizing hardware so programmers can optimize to the platform again instead of getting lost in APIs and driver bloat.

The only downside is the difficulty of upgrading hardware, but CPUs (and GPUs) are basically blackboxes to the End User already and no one complains about not being able to upgrade just the L1 cache (or vram).

Imagine a future where most end user MOBOs are essentially just a socket for a socketed-SoC standard, some m.2 ports, and of course the PCI slots (with the usual hardwired ports for peripherals). Desktops/laptops would generate less waste heat, computers would use less electricity, graphical software developement would be less of a fustercluck (imagine the manhours saved), there'd be less e-waste (imagine not needing a new mobo for the new chipset if you want to upgrade your cpu after 5 years), you'd be able to upgrade laptop PUs.

Of course the actual implementation of such a standard would necessarily get fuckered by competing interests and people who only want to see the numbers go up (both profit-wise and performance-wise) and we'd be back where we are now... But a gal can dream.

From an outsider perspective (I haven't used Nix at all), the downsides I see are that it's extra software on top of the defaults for any given distro, it's not optimized for the distro (meaning it might pull in dependencies that already exist or not use distro specific APIs/libs), and it doesn't adhere to the motivations of the distro (e.g. not adhering to the DFSGs for Debian).

And of course, most of the packages are community maintained and there's the immutability, which might be a hinderance to some use cases, but not for me.

All in all, not really the worst if you're not worried about space or getting the absolute most in performance and not an ideologue, but it's enough to make me stick with APT. I chose Debian because of its commitment to FOSS, not the stability nor performance.

Currently virt-manager on top of qemu/kvm on Debian 12. It was the easiest to get to emulate a TPM on my ancient hardware (9ish years old, but still powerful).

I'm learning enough about the backend that I'm hoping to get off the Redhat maintained software and only use the qemu cli, maybe write my own monitor with rust-vmm when I learn enough rust to do so.