That&#x27;s a good point. I&#x27;ve been ignoring learning Git as long as I can but almost everything on my todo list heavily uses it. Or ties into it as you said. So, I&#x27;m going to have to bite the bullet and learn it.<p>Yet, I swore Git fans told me its decentralized design avoids single points of failures where everyone has a copy and can still work when a node is down just not necessarily coordinate or sync in a straight-forward way. This situation makes me thing, either for Git or just Github, there&#x27;s some gap between the ideal they described and how things work in practice. I mean, even CVS or Subversion repos on high availability systems didn&#x27;t have 2 hours of downtime in my experience.<p>When I pick up Git&#x2F;Github, I think I&#x27;ll implement a way to constantly pull anything from Git projects into local repos and copies. Probably non-Git copies as a backup. I used to also use append-only storage for changes in potentially buggy or malicious services. Sounds like that might be a good idea, too, to prevent some issues.