spiffeeroo

WebP can be lossless or lossy compression. However, it is not easily apparent which compression mode is used for a given WebP file.

Google says lossy WebP is 25 percent smaller than JPEG and lossless WebP is 25 percent smaller than PNG.

Microsoft is an advertising company just like Google, Meta, Amazon, and Apple. Bing search and Edge browser in Windows are a few ways ads are shown to users. Netflix is using Microsoft ads network for their platform to show to their subscribers. Companies pay a lot of money to get preferential suggestions/queries on their stores and search engines.

https://about.ads.microsoft.com/en-us/solutions/microsoft-audience-network

Microsoft generates over 10 billion US Dollars per year in revenue from their advertisement division. The revenue growth from their advertisement business is growing exponentially at around 10 percent every year.

Are you talking about addresses like 192.168.x.x? Do you have subnet routing enabled in Tailscale?

That just means the TPM will not auto unlock the encrypted disk. You would have to unlock with whatever LUKS password (or key file) you set for that drive. There is optionally a TPM master key you can export that is similar to the Microsoft Bitlocker password (40 digit number iirc), that Lennart mentioned in his blog. If you deleted any other key slots and do not have that TPM master key, you will not be able to unlock the LUKS drive.

If you look at that freedesktop manpage I linked, it states some of the PCR values and what each one measures. When you enroll a PCR, that value is stored in the TPM. If anything differs between the system and the TPM, the TPM will refuse to unlock that encrypted drive.

For example, PCR 0 measures your motherboard UEFI firmware. If you update the firmware, the TPM will not unlock your LUKS drive until you re-enroll the drive once again. Is is a personal choice, but enrolling certain PCR into the TPM can be more inconvenient.

I think pcr 7+8 (for grub) or pcr 7+12 (for systemd-boot) should be okay. The more pcr you add, the higher likelihood you need to re-enroll after updates.

https://www.freedesktop.org/software/systemd/man/systemd-cryptenroll.html

The reason why using your own keys can be a problem is if you exclude the Microsoft certificates, then oproms from graphics cards stop working. You have to add the Microsoft certs after using your own key for the top level platform key.

For Debian, if you use out of kernel modules like Nvidia, you have create signing keys and edit a config file so dkms to sign those modules for those modules to work with Secure Boot. Instructions are on the Debian wiki.

https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key