Jyrki 🐾 @nilsding@pounced-on.me

The way he moves

YaST for fun

absolutely losing my fucking mind at this video from the wikipedia page for the physics engine "phyz"

@Lyude on top of that, while an application having lots of CVEs could mean it is insecure, it also could mean literally a ton of people use this application so it's tested for security holes almost constantly and thus the existence of more CVEs is more representative of security issues being found and fixed in a timely manner

Just gonna put this out here: it may be very tempting to look at a bunch of CVE numbers and think to yourself "wow, this application has so many numbers! It must be insecure" but lemme point out some things I've learned from handling CVEs:
CVEs are valuable, but read them also because oh boy I've seen plenty of nonsense CVEs that were not actually reproducible, were filed about unrelated components, etc.

oh fuck

💻 💦 🐶

Like this logic is toxic in the industry. I don't mind spending my evenings learning new things but there needs to be a balance and this doesn't promote that.

Would be nice if Facebook SDK remained broken so people would be forced to remove it from their apps...