I kinda like YAML for simple configuration files, but the YAML spec is borderline insane.

https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

And don’t get me started with ansible, it never works the way I think it should and almost every playbook or role I write is a pain to get right. When it works, it’s a really nice tool and I couldn’t manage my homelab as efficiently without Ansible, but it frustrated the hell out of me way too often.

It’s fucking BILD. Tell me when those bastards spew something else than disinformation and hatred and maybe I’ll care. Otherwise it’s just business as usual.

if the database “can’t handle it” […] that proves that they make poor choices.

Exactly, the database should never even have to handle the password in it’s original form and hashing algorithms don’t care about special characters.

This does not actually work, right? Right?

Oh hey, it’s me!

Video of the incident

You should check out Uptime Kuma which offers different monitor types. This should give you a good start for your own implementations. Or maybe you’ll find that Uptime Kuma already covers your usecase.

Interesting read! The follow-up about the biggest smallest PNG goes even more in depth about compression and produces a 1x2064 pixel PNG with just 67 bytes.

This patch is a week old, so hopefully you have already updated.

GitLab seems to have glaring security holes quite often. Surely this is in part because of the open source codebase and their bug bounty program, which incentivizes researchers to look for these flaws. I’m still baffled sometimes. I’ve read about a lot of > 9.0 CVEs while maintaining our GitLab instance, there was a 10 only three weeks ago. Thankfully our instance isn’t public.