People who can't fathom this also can't fathom that Iran offered to help the US invade Afghanistan because they wanted Al-Queada off their doorstep. Then we put them on the Axis of Evil and took 20 years to loose a war.
If this confuses you then you are extremely misinformed and operating on the ignorant notion that "radical Islamist" = "terrorist". The Taliban never embraced terrorism as a tactic. Unless you're so brainwashed that you think IEDs are terrorism. Islamic terrorism has almost exclusively been the domain of Wahhabists like Al-Queada and Islamic State
The Taliban is currently fighting Islamic State Khorasan Province, which is largely constituted of former collaborators of the coalition government. Everyone in the region would much rather have the Taliban as a neighbor than those genocidal freaks.
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.
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.
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.
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.
She also met privately with Netanyahu after his speech. She's definitely more aware of the electoral consequences of supporting genocide than Biden. That's an improvement. But to me its all hollow gestures for now. Candy coating for the election that will get dissolve once in office.
None of the actions at the protest went too far. All this is just asking for "less genocide" instead of "no genocide" which I view as genocide apologia.
The US has been playing with these kinds of lasers for over a decade now. Last I saw a demonstration, the laser wasn't powerful enough to just zap something. It had to focus on a warhead and heat it up until it exploded. It wouldn't work on a missile in flight. Maybe they improved it, but I suspect the introduction of slow drones like the Iranian Shahed made it feasible.
The cost per shot was pennies a decade ago. But how fast can they shoot these? It must be able to shoot fast and constantly if you want to deal with swarms.
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".
It can only recognize certain hotwords on its own, eg, Alexa. So its not recording 24/7 but it is listening 24/7 for hotwords. They could push additional words and start recording whenever they hear it.
This is unfortunately just a really good edit.