ma1w4re

Fuck yeah that kind of shit, I love it, let's go 😖🔫

Someone should make a script that generates the sticker with updated version numbers 😵😵😵

But it's fun though

That's IF the would be even able to pull the kernel. I know how government grants work here. 70% chance that the money gets stolen and work is outsourced to some bloke who doesn't know what git is.

When it fails I'm gonna laugh a lot.

I'm not gonna use this shit regardless. Even if it remains the only option for an OS in Russia, I'm gonna fucking smuggle a proper Linux distro in.

OH NO, I hope the fork will continue for a bit otherwise I'm so cooked 🥶🥶🥶

Can confirm same result when searching through searx instances, result provided by google.

List of files/pages that a website owner doesn't want bots to crawl. Or something like that.

And then the bus fell on its side, amen brother 🙏

Omfg I was also enlightened by this

Little addendum to the last part of About Fragmentation section, since I don't want to leave it unfinished and make people struggle if they follow my advices:

$HOME/.local/opt is a "usual" (there are few more, I prefer this one) location for pre-built (downloaded) and built-locally apps that you don't want to install system-wide.

For example:

1. I downloaded neovim binaries because I didn't have time to build em (lazy ass), but at least I did it from their git repository.
2. I untarred the archive using tar xvf nvim<press TAB>, or right clicked on the archive in a GUI file manager and clicked decompress.
3. moved nvim-linux-x64 directory into .local/opt, and renamed it to nvim (usually done in one command, if using terminal - mv nvim-linux-x64 $HOME/.local/opt/nvim)
4. Changed dir into .local/opt/nvim and found the executable, in our case something like ./bin/nvim.
5. I link that executable into a directory for binary files that lies on the PATH (system checks PATH it to find shit), like this - ln -s /home/<my nickname>/.local/opt/nvim/bin/nvim /home/<my nickname>/.local/bin/nvim this command requires absolute paths and creates a SYMBOLIC link (you can read up on that if you're interested). GUI file managers usually have functionality for creating symlinks, right click on file to find out.
6. Some distros include .local/bin to path by default, while others don't. Simple way to do so is open your .bashrc or .zshrc that's located in $HOME in a text editor, and somewhere close to the end of file write export PATH="$HOME/.local/bin:$PATH"
7. I close and reopen my terminal. Nvim is now installed, by hand.

Something like that. It's all done just for organization and quality of life.