

People are downvoting you, because while the Holocaust wasn’t the first nor last genocide, it still is unique. Your initial statement makes two claims, but you only refer to the one less controversial one in your “curious edit”.
People are downvoting you, because while the Holocaust wasn’t the first nor last genocide, it still is unique. Your initial statement makes two claims, but you only refer to the one less controversial one in your “curious edit”.
I think this is a good idea and wish you all the best.
Moderation will be key of course, but the rules ( http://diagonlemmy.social/post/108 ) sound good.
At the same time, if somebody doesn’t even want to think about HP, they can easily block the entire instance, no harm no foul.
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.
I don’t use react, but needed a decently looking frontend complement library that didn’t look dated, and found basecoat, which is shadcn but without react to be really neat.
Might be interesting for the htmx crowd here.