This was done out of an abundance of caution, I'm sure.
Can’t get hacked if you’re offline.
GitHub issue - resolved
101–110 of 169 posts
Re: GitHub issue - resolved
#102Git Docs... - https://git-scm.com/book/en/v2/Getting-Started-About-Version...
"...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."
"...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..."
"...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...."
Re: GitHub issue - resolved
#103One wonders if MSFT leadership will ever connect the dots between “hollowing out talent over the years,” “hiring freezes,” and “layoffs” to this outcome.
One wonders sometimes if that’s the goal.
Re: GitHub issue - resolved
#104Now's a good opportunity to ask about alternative Git hosts. What other services do HNers use? 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…
I have a vps with bare git repos, pushing via ssh. A selection of these has hooks set up to mirror all pushes onto github/gitlab/$platform, but these are write-only.
Re: GitHub issue - resolved
#105I 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".
I think you meant "I dunno what's down..."
Re: GitHub issue - resolved
#106> We’ve identified an infrastructure change that has been rolled back and we are monitoring recovery.
From github status
Re: GitHub issue - resolved
#107One has to ask oneself... would this have happened without the Microsoft acquisition?
Re: GitHub issue - resolved
#108Everything is green now!
Re: GitHub issue - resolved
#109https://www.githubstatus.com/incidents/52z0j6phhnjs
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
> However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
Another popular one is "elevated API error rates" when the error rate is 1.