"A qsort vulnerability is due to a missing bounds check and can lead to memory corruption. It has been present in all versions of glibc since 1992. "

This one amazes me. Imagine how many vulnerabilities future researchers will discover in ancient software that persisted/persist for decades.

My most paranoid config is disabling Ipv4

That's it. If someone wants to attack me, they will need to adopt IPv6!

IP is like an address to a big skyscraper where a company operates. You are the delivery man and must go to 201.154.76.19 and deliver something. When you get at the reception, you tell them you have a package to deliver to Mrs HTTPS, at room (port) 443. Since Mrs HTTPS is well known and has cleared your entry before, you're allowed to enter this room and only this room.

If you were to get at the same address and try to access other rooms you would either get refused because they are closed, or if open, someone would specifically need to be in the room so you can deliver something

Malicious actors that wanted access to the building could try to disguise their deliveries and enter the building, that's why the default policy of most firewalls is "reject" and you specifically need to open a port and have a program listening to it if you want incoming connections.

For those who use Wayland and autostart, don't forget to edit

/etc/sddm.conf.d/kde_settings.conf

from KDE5: Session=plasmawayland

to Plasma6: Session=plasma

to confirm the exact name, check what is available under /usr/share/wayland-sessions/

if you're stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related, then fresh install plasma-meta or plasma group and it should work

I didn't know memes could smell like they're old through the screen until I saw this one

Google logo before Corporate Memphis bullshit and the dude using a feet to hold his cup of tea just like the classical antiquity raptor, it's just perfect

I thoroughly backup up my slow nvme before installing a new faster one. I actually didn't even want to reuse the installation, just the files at /home.

So I mounted it at /mnt/backupnvme0n1, 2, etc and rsynced

The first few dry runs showed a lot of data was redundant, so I geniously thought "wow I should delete some of these". And that's when I did a classic sudo rm -rf in the /mnt root folder instead of /mnt/dirthathadthoseredundantfiles

Already switched to AMD to enjoy it

That'd be over 1TB with zram on

Considering it's almost always 30°C+ 60%+ RH at least half of the year where I live, yes

Refrigerating them increases their shelf life significantly in these conditions

It's probably less effective in other cooler and drier climates

Interception by a third party is highly unlike, as the transport layer of basically everything is encrypted nowadays. What is left unknown is what can Meta do once the file is on their servers, as you'll have to trust Zuckk's word and Zuckk's encryption

lol my cat actually meows and asks to be vacuumed

Most things would be solved if mainteners EVER updated their app's electron version or stopped doing custom things with it and just let electron read $XDG_CONFIG_HOME/electron-flags.conf

For those who use Wayland, don't forget to edit

/etc/sddm.conf.d/kde_settings.conf

from KDE5: Session=plasmawayland

to Plasma6: Session=plasma

to confirm the exact name, check what is available under /usr/share/wayland-sessions/

if you're stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related + remove orphans , then fresh install plasma-meta or plasma group and it should work

AMD is the gold standard for general user PCs in the last 5+ years. Intel simply cannot compete at the same energy expenditure/performance. At the same/close price/performance, Intel either burn a small thermonuclear power plant to deliver comparable performance, or simply is worse compared to similar Ryzens

Ryzens are like aliens compared to what AMD used to be before them

So I'd go with them

As for the GPU, if you want to use Linux forget Nvidia

I switched to systemd boot when that happened, and it's been so smooth ever since

Just don't upgrade for a while and you become debian

It's not like windows forcing you to reboot every Tuesday so Edge can come back

I finally switched to AMD after 3 years in Linux, and man I didn't even know I was suffering until I booted with AMD and didn't have to take care of several env variables and separate modules for hw acc

It just works

Does anyone have the ref to the original art?

It's not exempt from happening; however, it rarely ever updates and has less complexity/functionality than grub, which makes it less prone to error happening (be it from the developers, or from the user like me trying to theme it :))