Linux and Windows compress it too, for 10 years or more. And that’s not how you avoid zip bombs, just limit how much you uncompress and abort if it’s over that limit.

There are some examples of projects that use CleanURLs db in its readme but most have not been updated for a long time.

There are plenty of sites that use more than one parameters. It’s true that a lot of sites now use the history API instead of url parameters but you can still find plenty, and you have no garante about the parameters order. Any site with a search page that have a few options will probably use url parameters instead of the history API. It’s easier to parse and will end up being shorter most of the time.

Well for youtube it’s quite easy, there are only 4 useful parameters that I can think of, the video id v, the playlist id list and index if it’s a playlist and the time t if you’re sending a specific time in the video. Everything else can be removed. Here’s what uBlock Origin with the AdGuard URL Tracking filter list:

! Youtube
$removeparam=embeds_referring_euri,domain=youtubekids.com|youtube-nocookie.com|youtube.com
$removeparam=embeds_referring_origin,domain=youtubekids.com|youtube-nocookie.com|youtube.com
$removeparam=source_ve_path,domain=youtubekids.com|youtube-nocookie.com|youtube.com
||youtube.com^$removeparam=pp

There is no logic as to which parameters is useful and which is used for tracking. But there are databases.

Here is the one for the CleanURLs extension and here is the one for the AdGuard URL Tracking filter list (which I recommend everyone should enable in uBlock Origin).

It’s better to avoid re-encoding as it lose quality.

It would be great if there was a way to scroll the article directly, without leaving the site and going to Wikipedia. Like scroll left and right to change article and scroll down to read.

I did: a) as said elsewhere in this post steam auto update, the package version is not relevant. b) this is 5 years old.

I don’t think you should trust it more.

The link you posted is about using steam with NTFS and the installation method has nothing to do with it.

Even after reinstalling steam with the steam.deb file it shows the same error

I never heard that and never installed Steam without a package manager. Be careful not to listen to everyone’s advices.

I’ve never seen the !0 and !1, it is dumb and indicates either young or terrible devs.

Boolean(window.chrome) is the best, !!window.chrome is good, no need to test if it’s equal to true if you make it a boolean beforehand.

I don’t understand why but OK.

That would be very weird. I gather that Mint use Ubuntu’s packages so it should be OK. Did you try it?

I don’t really know mint but why not install it through your package manager?

Is this left-wing?

https://en.wikipedia.org/wiki/Compulsory_sterilisation_in_Sweden

https://en.wikipedia.org/wiki/State_Institute_for_Racial_Biology

Well in the end I think I’m needlessly nitpicking. It doesn’t matter if it’s strictly immutable or not. What matter is that it has the good parts of reproducibility, immutability and declarativity.

Isn’t immutability related to the root filesystem being read-only? I can write on my root filesystem, even if it’s mostly links to the store I can replace those links.

Yes, or use flakes which gives you a lockfile pinning everything. But this is related to reproducibility, not immutability.

I’ve had NixOS absolutely refuse to run some compiler toolchain I depended upon that should’ve been dead simple on other distros, I’m really hesitant to try anything that tries to be too different anymore.

Yes, some toolchain expect you to run pre-compiled dynamically linked binaries. These won’t work on NixOS, you need to either find a way to install the binary from nix and force the toolchain to use it or run patchelf on it somehow.