F2 is universal, it's been there since before Microsoft. It also works on Linux and most independent software.
This. The guessing part comes from the time it takes to do the tasks, but you know the number of tasks. So a progress bar should only reach 100% when all the tasks are completed.
For example, you might have a big process that performs 3 other small tasks and then finishes. You could reasonably assume that each small task is 33% of the big process, so after the first finishes you get 33% progress, then 66% after the second and 100% after the third. When the bar reaches 100%, the third task has finished, so your process has finished too.
What you don't know is how much time each small task takes, so if the first task needs 20 seconds and the following tasks take just 5, you'll spend 2/3 of the time on the first 33% of the progress bar, and then the remaining 66% gets done in 1/3 of the time.
Depends on the system, but normally, the OS provides a way to encrypt a file using the user credentials. It's completely seamless while the user is logged in and using the computer. It's true that any program running with the user privileges and within its session can open the file, but once the user logs out it's unreadable.
I don't know about the framework laptop, but about the Minecraft question:
Yes, you can absolutely run Minecraft on Linux. It runs on top of Java, so it doesn't really see the difference between the 2 OS. In fact, I've found that Minecraft runs faster for me on Linux than on Windows. The only thing that might not work is the official launcher, but that can be easily replaced (with the added benefit of improved functionality). I can recommend Prism Launcher, but really anything works.
About Bedrock, that's a different story. Microsoft revamped the PC port of Bedrock, and now calls it "Minecraft for Windows". It's fully compiled, and it won't run natively on Linux. However, I still believe it can be made to work with some Wine trickery.
It is surprising how much the landscape changed in just 5 years. All the right wing parties got a boost, but most importantly, the ultra right and christian right parties. All those are surely going to want to implement ChatControl and measures like that because "We need to protect our children!"
I'm also scared of all the new Q-Anon type parties that last time didn't even exist and this time won a few seats. Ultra right conspiracy theorists that now have more seats than even the pirates.
Also look at the results from Gernany or Austria. AfD and Orban. Pro nazi and pro russian parties. We're going back in time for a remake.
Discord customer service is abysmal. I've had to contact them twice, and twice I have been ignored. They answer 10 times with the same AI generated response: "Have you tried turning it off and on again? Have you tried logging off and on again? Have you tried resetting your password?" I tell them I have tried everything, and they still answer with the same response, just paraphrased a bit differently.
🔫🔫🔫
If you use Arch, you aren't really affected. As far as we know, the backdoor only affects SSH if it is linked against liblzma, which is a requirement for libsystemd. However, Arch doesn't use that, so SSH has probably been safe. However, you should still update, because we don't know if the backdoor could've been used in other ways.
Note that if you update, xz 5.6.1-2 will be installed. This is a safe version. However, if you run xz --version, it will still report version 5.6.1.
Wayland, Texas. According to wikipedia it had a population of 100 people in the year 2000. AFAIK it's a ghost town now.
I know that town because I once read a "fun fact" about the Wayland Protocol that said its name was chosen for being the name of an actual town, which (supposedly) cannot be copyrighted.
People are really creative when it comes to potholes, huh?
I do like this way of dealing with them though. You get a laugh, it doesn't harm anyone and gets the potholes noticed.
you can't really hot swap the kernel, because all of the system runs on it.
you'd need to stop the system (you can save its state and recover where you left), reboot to load the new kernel and let it take control.
however, there are some distros and programs that allow you to hot swap certain parts of the kernel (mainly drivers) without rebooting. Note that, even though the system doesn't reboot, most packages still need to be restarted for them to pick up the new driver.
B-but capitalism breeds innovation!