30p87

Aha, hab ich dich doch mal hier in feddit gefunden. Ich wusste gar nicht, dass du auch außerhalb der Matrize existiert lül

Because even though it saves over 29 MB, it also takes more than 20 times as long. And that's just on my laptop, 1920x1080 + 2*1680x1050. On my PC it's even worse.

I have thousands of GB of high speed storage, Gigabit internet, but only a Ryzen 5 2600 and a i5-1145G7.

Currently the server(s) are in my room, which is so messy my dad probably wouldn't even enter it voluntarily. And in the case grub/fstab/crypttab/etc. are messed up, which is probably the most common error, he probably couldn't solve it by himself. Soon everything's gonna live in its own little room in the basement, so it's gonna be accessible easier actually.

And then you wonder if you typed reboot or poweroff

(Or 6/0 for the debian people)

I'm 150+km away from my server, with literally everything on it lol

Yes. But in theory it's still a performance hit, and as I have enough local storage (and typically use services with high limits), and I'm too lazy to change grims config just for discord, I never changed it and used Vencord instead.

Because it was never a problem. It's a little bit faster for encoding and decoding, and no service ever had problems with the file size. Especially not my selfhosted stuff. Every service, except discord. As I now have resorted to using Vencord or just uploading most media to Nextcloud, I don't have that many issues with it anymore, anyway.

I am using png. Level 0 compression tho and in 4k (3840*2160), sometimes even 4k + 2*1440p (2560*1440), but it's already too large with just my main 4k monitor.

And standard screenshots of my desktop are ~30mb, I was lucky to upload it lol

I had that issue for months. There is no real solution afaik. Apparently, reading the NVM checksum is just not possible on Linux with this chip. It always defaults to 0xFFFFFF I believe. In theory you could write some value, to reset it, but it gave me some permissions error. I resorted to get the source of the kernel, patch out the checking code, compile just the module and then install it. I created a PKGBUILD for it, and I'm currently trying to make it a DKMS package, so you don't have to reboot first to manually rebuild it.
As you use Debian, you'll need to create a manual compiling script, but here are my PKGBUILDs for reference: https://git.30p87.de/30p87/e1000e-nocksum-kerne Note that you need to swap out the kernel source link to the source of your current kernel version.

The current problem is, that you need to reboot to update to a new kernel version, which then means the custom driver will not work anymore, and you need an internet connection to rebuild it, as it will need the most recent kernel version. So never kernel update without wifi in reach.

I will first make it a DKMS package, to ease some of the pain, and then see if I can make it debian compatible.

Also have the same ass specs, apart from the SoC itself, but cost 50% more.