Mostly yes, but there are some closed source services which are still good options for this specific threat model.
And I just thought the clear explanation of the why combined with the list, makes this an excellent blog to send to people who don’t get it yet.
The list itself is something most of the people in this community know already, but you might want to send this when someone asks “why?”
Took a look at the specification, this is what I found:
For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.
So they should retry. Note that should is not the same as must. So there is no obligation. There is no timeline in the spec about for how long or how often retries should be done. The wording says network error.
My interpretation: the spec leaves a lot of room for implementations to differ. Network problems don’t normally last for days though. I’d guess that if your server is down for 5 minutes, you’ll still receive most or everything you’d normally receive. I wouldn’t trust on that if your server is offline for more than a day.
GitOps + Renovate.
Tools that allow you to work GitOps (everything is defined in text files in Git) are:
Here’s a nice starter template for running your own Kubernetes cluster via GitOps with Renovate pre-configured: https://github.com/onedr0p/cluster-template