Except solar. And wind. And hydro.

can you explain the joke, i work at cloudflare

Amazing tan lines.

You can start by moving your development workflows (pull requests, issue tracking, etc.) to something like codeberg. You can continue publishing your PyPI package from Github by just pushing your code from codeberg to Github.

Eventually you can also move the publishing pipeline over as well. I don’t know how complicated your library is, of course, but in simplest cases it’s a matter of rewriting a config file in a slightly different way.

The design is very human.

YOU ARE UNDER ARREST FOR FELONY CONTEMPT OF BUSINESS MODEL

To save you 50 clicks required to get through to the t-shirt content, it said: "god (Allah)" followed by "is lesbian".

wow so lazy just pressed ctrl-ξ ctrl-ψ

I think the basic premise of this question, that Windows and Linux somehow have a different foundational security model that is or isn't based on passwords, is not really true. Passwords play more or less the same role for any modern operating system -- be it Linux, MacOS, Android, iOS, etc.

The only major difference is that instead of UAC, Linux has a variety of options (sudo, policykit, run0), which are implemented differently across different distributions. If your privileged user doesn't have a password, in some cases this could lead to any program being able to elevate their privilege quietly, unlike UAC.

However, in many distributions you can set up a user with a password and enable passwordless local login, which would be almost equivalent to windows with no password.

Answering your question directly, the major threat to most consumer users is physical compromise or theft of device. Your statement that "physical access is game over" is not entirely accurate: disk encryption with a password is a very strong protection against unauthorized data access, but you need to use a password (doesn't matter if it's Linux or Windows).

Yep, they technically didn’t claim it was to make it more secure.

Alyx

That’s a fairly common fingerprinting technique. A lot of sites use this and similar techniques (e.g. GPU fingerprinting, font fingerprinting, etc.) See https://developer.mozilla.org/en-US/docs/Glossary/Fingerprinting

Or try https://amiunique.org/ for a live illustration how that works.

Go to Preferences -> Audio -> Replay Gain mode and set it to "Album" (if you're listening to whole albums) or "Track" (if you're mixing it up). This will let VLC read the ReplayGain[1] tags in your files and adjust playback volume accordingly. Chances are high that a lot of your collection already has these tags, and you won't have to do anything else. If some of your files don't have these tags, just run a tool (https://github.com/complexlogic/rsgain for example) to generate them.

Also if you make a typo you can quickly fix it with ^, e.g.

ls /var/logs/apache

^logs^log

In liquid form?

That basically is Die Hard.

https://addons.mozilla.org/en-US/firefox/addon/don-t-fuck-with-paste/

Not even a good Terminal film.

You can open developer tools, download one of the files, then right click the request in the Network tab and select “Copy as curl command”, this will generate a curl command with all the headers and cookies.

alt-f4