I have never trusted them, I always considered many of Signal’s decisions highly questionable, and I think they are either pressured into them by the US government, cooperating in what they think are limited and carefully-implemented ways while claiming and perhaps even believing they are fighting the good fight, or maybe they are just a psyop honeypot to begin with. I cannot trust them, and if they truly wanted me to, they would not do so many things that require me to trust them.

This is good thinking, and you may still want something like this anyway, as there’s always room for additional documentation, but let me propose an alternative that takes this good way of thinking a step further:

Infrastructure-as-code means my code is my documentation. How’s it configured? Look at the code. What’s it doing? Look at the code. Don’t understand why it’s doing that? Use more descriptive names for things and write more self-explanatory code. Is the code out of date with the current state? Stop implementing things manually and make the code run automatically instead so it’s never out of date anymore.

I have complete confidence in my setup and life is easy now. Except when the IAC breaks. But that’s rarely a panic situation, just mildly frustrating.

glorified autocomplete. profit-seeking trojan horse for propaganda purposes. self-inflicted workforce deskilling. unsustainability generator.

I hate python packaging. pip freeze is about as complicated as I’m willing to get with it, because all the other options horrify me.

The whole point of status pages is to minimize and deflate the impact. The pleasantly-high percentages even during absolute catastrophes is an intentional design feature. The percentages are not going anywhere. The percentages will continue until reliability improves. Which it won’t.