

Thanks for recommending it, it does look really nice. I’ll definitely check it out when a fitting project comes along.
Thanks for recommending it, it does look really nice. I’ll definitely check it out when a fitting project comes along.
I mean, this is a light-hearted meme, no offense to the people actually fixing things.
But at a company like GitHub the first status update should be and probably is created semi-automatic (just approved by a human). Afterwards they should follow a process to assign an incident communication lead, who takes over all communication so that the rest of the team can work on fixing the incident.
@GitHub: Hire me for more incident response tips from the backseat! :P
I’m actually not that into actual self-hosting (it feels too close to my day job). But i love the idea of it, and actually do host my own RSS Reader: It’s selfoss (PHP + SQLite, so, very simple) and i have been using ever since google reader shut down. It runs on my uberspace.de instance.
Awesome, I didn’t know that either! TIL