Hi folks, I’m making another tech-stack recommendation. Previously, on Awful, I noted that below 87.5% availability, whether a service is up is effectively random chance. We’ve reached that point for GitHub’s Platform, which includes components like Actions, Copilot, Pages, and the core API of issues and PRs. I do not have confidence in GitHub’s owners or operators to remedy this situation, so I cannot recommend it professionally nor to neighbors. As a bit of nuance, note that Pages seems to have relatively decent availability and is often up even when the rest of GitHub is down, so static content hosted on Pages can be deprioritized for migration.
The thread is open on Lemmy. I’m interested in your thoughts, particularly around alternative forges, alternative paradigms for forges, community-driven plans for migration, strategies for migrating, and tools that ease the burden of maintaining many git repositories.
Can’t believe I’m nerd-sniped this easily. Very technically, the point at which a service should be considered unreliable or down is at γ nines, where γ = 0.9030899869919434… is a transcendental constant. γ nines is exactly 87.5% availability, or 7/8 availability, and it’s the point at which a service’s availability might as well be random. (Another one of the local complexity theorists can explain why it’s 7/8 and not 1/2.)