Now's a good opportunity to ask about alternative Git hosts. What other services do HNers use?<p>I've been unwilling to host any personal projects on GH after Copilot launched and it because clear that GH/MS doesn't really respect the authors of the code they host. Honestly open source in general has gotten a little less compelling to me after Copilot. The recent security issue at GH has also turned me off even more on Git hosting services.<p>For closed source projects maybe it's just best to store encrypted backups off site and spin up a self hosted option whenever collaboration is needed. Seems pretty inefficient though.
I feel like HN could just have a traffic monitor that adds a little icon to the main page. Like "I dunno what's up, but there's a LOT of y'all here right now, so something probably is".
Because this needs to happen as one prepares to push to day's last deploy. Back to backups.<p>Have backups for critical systems, people. In my case, it's building docker containers locally and luckily deploying to one server via ssh.
Git Docs... - <a href="https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control" rel="nofollow">https://git-scm.com/book/en/v2/Getting-Started-About-Version...</a><p>"...The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, this has been the standard for version control."<p>"...However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything..."<p>"...This is where Distributed Version Control Systems (DVCSs) step in. In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it. Every clone is really a full backup of all the data...."
Hmm this is quite an incident, I haven't seen Github reject all pushes to all repos like this in quite some time.... hopefully not SSH key related
It goes down every month like I said before [0]. The last time this happened was 2 days ago [1] then weeks ago [2] and it is evident that it is falling apart in front of us.<p>First, it was the RSA key leak in [1][3], then the site's key expired causing down time again [2] and now this.<p>I don't think anyone can tell me with a straight face that GitHub was any more reliable or better when Microsoft acquired it. It is now worse off.<p>Nothing has changed except for more outages and downtime.<p>So so reliable. /s<p>[0] <a href="https://news.ycombinator.com/item?id=35004629" rel="nofollow">https://news.ycombinator.com/item?id=35004629</a><p>[1] <a href="https://news.ycombinator.com/item?id=35295216" rel="nofollow">https://news.ycombinator.com/item?id=35295216</a><p>[2] <a href="https://news.ycombinator.com/item?id=35003741" rel="nofollow">https://news.ycombinator.com/item?id=35003741</a><p>[3] <a href="https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/" rel="nofollow">https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-k...</a>
Looks like it's back and the status page reports it as green, however GitHub Actions builds are not triggering on push as usual when this happens, so for me it doesn't seem to be fully recovered yet.
Suppose you start your day by downloading some code from GitHub to work on. This morning you would be stuck. Do you save code on your hard drive or company servers or GitLab to handle this risk?
One wonders if MSFT leadership will ever connect the dots between “hollowing out talent over the years,” “hiring freezes,” and “layoffs” to this outcome.<p>One wonders sometimes if that’s the goal.
Only code with Github is replicated locally, not everything else like wiki, issues, etc.<p>That's something I love about Fossil.<p>Everything with Fossil (wiki, issues, code) is replicated as well.
I wonder if it has anything to do with them updating their RSA SSH host key (<a href="https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/" rel="nofollow">https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-k...</a>) 3 days ago.
I feel like events like these are the new "compiling".. <a href="https://xkcd.com/303/" rel="nofollow">https://xkcd.com/303/</a>
Also seeing unicorns, mostly for "No server is currently available to service your request.". If I don't get a unicorn, the page takes a long old time to load.
Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.