Image isn’t real

Risk instruction is not very accurate since even arm has them but microops still exist

Can you not create another release by the same name?

I don’t understand how Ai can understand ‘3nr1cH 4n7hr4X 5p0r3s’. How would that even be tokenized?

I’m convinced Arch with archinstall is the easiest Linux to use for users competent with computers. It just requires that the user isn’t afraid of command line interfaces.

I’ve tried the Mint, Ubuntu and uBlue. Had something go wrong with each. Mint didn’t install graphics drivers, Ubuntu had nonsensical design with snap and uBlue corrupted the boot order after a month.

With distros designed to just work it isn’t easy to fix issues when they come up. With Arch there’s no expectation that things work by default, so when something goes wrong you can just make it work again.

I don’t follow your thought process. I didn’t say every running process could kill the lock screen or if it can kill the lock screen it can access everything else, I said any process that kills the lock screen has to be running. And as the attacker with physical access doesn’t know the password they can’t run anything to kill the lock screen. The only way for them to unlock it is if they already have malware on the device, in which case their physical access isn’t the cause of the problem.

How so? The lock screen is to prevent physical access while you’re away, and an attacker can’t kill it without having access in the first place. Any process that can kill it would already have access to your session.

Them who? What happened?

… Brazil is one of the first countries this’ll go into effect and I also remember something about how that first batch of countries was chosen because their governmemts support this change.