Imagine asking a DoD contractor to make their shit cheaper.

Still hosted on GitHub, a property of MicroSoft.

We’re talking about poisoning a single person not a gas cloud. Poisoning a single person vs drone striking a wedding.

Nerve agents compared to drone strikes look humane and civilized.

The legal reasons was because the Linux Foundation is based in the USA and the targeted devs worked for companies explicitly sanctioned by the USA. Linus said he knew and trusted the devs he was forced to delist.

The Linux Foundation needs to relocate to some stable neutral country like Switzerland.

Every other square mile is cleared for logging as some sort of forestry preservation/logging compromise. The spaces logged are clear cut.

Western Oregon

Its all over the pacific northwest. Washington, Oregon, Idaho, Montana. Its not a specific spot.

That’s when you rotate the proxy. By default most residential proxies will give you a new proxy for each request unless you specify.

Pro-tip for webscrapers: using AI to solve captchas is a massive waste of effort and resources. Aim to not be presented with a captcha in the first place.

Worse is when its asking for crosswalks and its clearly a rumblestrip.

fwiw headscale is pretty easy to self host and has minimal system requirements.

I think PopOS can safely assume that its being installed on a laptop with only one drive. If there’s multiple drives involved then the setup gets far more complicated as you then must go to something like an LUKS on LVM setup. Basically, for a desktop there’s no safe defaults for FDE.

I’m pretty sure all the major distros have FDE as an option in the installer its just never on by default. Fedora does the same but with BTRFS on LUKS. I’m sure Debian does. Someone else says OpenSuse does. Maybe some derivative distros don’t but I suspect the ones with an graphical installer do.

Looks like they use eCryptFS. Never heard of it before so thats neat. I can see using it on systems where you can’t reinstall the system with Dm-crypt but it most cases I suspect Dm-crypt is a better alternative.

Idk if its faster or slower than Dm-crypt.

The standard route is to decrypt on boot. It happens after GRUB but before your display manager starts. IDK if there even is a setup that has you “decrypt on login”. Thats sounds like your display manager (sddm for KDE) is decrypting system which is not possible IMO.

Unless your laptop somehow has multiple drives you’ll want to use the “LVM on LUKS” configuration. 1 small partition for /boot. The rest gets LUKS encrypted, and an LVM group is put on the LUKS container. Or you could replace LVM with btrfs.

This will require wiping your system and reinstalling so you have some reading to do.

• https://wiki.archlinux.org/title/Dm-crypt (aka LUKS)
• https://wiki.archlinux.org/title/Dm-crypt/System_configuration
• https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system
• https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LVM_on_LUKS

The arch-install script in the live iso has options for full disk encryption.

If you suspend to RAM your system will stay unencrypted, because your ram is not encrypted. if you suspend to disk (aka hibernate) your system will be encrypted. You go through the boot loader when waking from hibernation but it just drops you off where you left off.

You need a swapfile for hibernation so make sure its inside the LUKS container.

Unironically try turning your computer off and on again.

Tmux settings are global and persistent. Just deleting your config files is insufficient. You have to kill the server and restart it. Uninstalling and reinstalling will not kill a running tmux server. tmux kill-server should work too.

Now if it persists across reboots, then there must be a file still lingering somewhere. If you are sure your home directory is clean you can try searching whatever you installed in /etc.

This is all assuming you’re trying to go back to a clean slate and failing. If the borked status bar is the result of your current .tmux.conf, then you’ll have to post that.

Its going installed binary is rg.

Who actually hates on declarative/immutable distros as a concept? Its always the actual usability of the specific implementations thats the problem. Stale packages, poor documentation.

We would easily be able to tell if an Alexa was constantly streaming audio data by monitoring its network traffic. It’d be just a wasteful inefficient implementation to stream everything 24/7. Makes much more sense to only start recording when it hears certain keywords that it can recognize locally beyond “Alexa”.