Several reasons

• If a private key leaks, a shorter certificate lifespan limits the fallout
• Faster upgrades to new cryptographic standards. If some of the crypto methods used get broken, short lived certificates means they get replaced with newer methods faster
• Short lived certificates force sysadmins to automate the renewal process. This prevents expired certificates due to forgetting the manual renewal.
• Certificate lifetime and domain ownership mismatch. You could buy a 2 year certificate for somedomain.com and then sell the domain or just let it expire and have it picked up by someone else. You then have a valid certificate for a domain you no longer ow and you could MitM traffic for the new owner’s website.

This is typical american carbrain shit. Is there any other country where the kind of car someone drives is even a consideration in choosing a romantic partner? I’m dating your car.

UPNP is a security nightmare, better to never enable it at all or if you must only for those networks where you need it.

I don’t think NDA’s cover hiding illegal activity.

They used to have dishwashers but those were made illegal when they passed the 13th amendment back in 1865.

If no one trains the next generation of developers, who will maintain and build the systems of the future?

Senior developers like me, for a price.

I don’t understand how you expect the verification of a physical book to work. You’d have to scan/OCR the entire book to verify the signature.

Alternatively you could do a hash/signature per page to make verification of a single page easier.

Many public keys chain-linked with one master key - are just for example

Have a look at Merkle trees.

Just use the App Store. Very few OSes as privacy respecting as iOS, certainly not we-pretend-to-be-open-source Android.

No joke. Google Play Services isn’t even available on iOS.

None of them require Google Play Services if you use their iOS app.

fzf fuzzy finder. Great tool to quickly find those files you were looking for.