91–100 of 721 posts
Earlier quoted context omitted.
Most services, even if they aren't the size of Github, can't change their DNS provider on a dime.
It's not a question of switching; you can host your DNS records at multiple providers.
Earlier quoted context omitted.
And I'm so damn tired of people complaining about cost to run stuff locally. The true cost of not having some basic stuff setup locally, even for backup purposes is when situation like this happens. It does not take long time or resources to download all of the libraries, with corresponding docs to a local server, or even your laptop. It is not complicated to have all of the new issues sent to an email to have a vers…
>And you don't need a sysadmin to administer all of that. I disagree with that. If you have a server, you need a sysadmin. End of story. Who is going to secure the system and setup ssh keys? who is going to run updates? who is going to monitor for security issues? who is going to run backups? who is going to secure those backups? who is going to oversee the installation of the network, the battery backups, the racks,…
I'm a GitHub employee and want to let everyone know we're aware of the problems this incident is causing and are actively working to mitigate the impact. "A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time." is the content from our latest status update on Twitter ( https://twitter.com/githubstatus/status/789452827269664769 ). Reposted here since some peo…
If this is consistently a problem why doesn't Github have fallback TLDs that use different DNS providers? Or even just code the site to work with static IPs. I tried the Github IP and it didn't load, but that could be for an unrelated issue.
Earlier quoted context omitted.
why?
Because America is an Orwellian hellhole, gawd, haven't you read animal house 84?!
Earlier quoted context omitted.
>We don't know who is doing this, but it feels like a large nation state. China or Russia would be my first guesses. Why not the USA?
It doesn't make a whole lot of sense for the USA to take down the internet, as they benefit the most from it. A significant fraction of that economy is based on it, much larger than in the cases of China and Russia. It would be like the owner of a coal mine campaigning for a carbon emissions tax: maybe there's something we don't know, but from the information we have it seems unlikely. Note that this wouldn't rule ou…
I'd be more willing to put my money on someone attacking an entity downstream who is normally immune to DDOS attacks of this size.
Earlier quoted context omitted.
Because America is an Orwellian hellhole, gawd, haven't you read animal house 84?!
the number of people missing the sarcasm in your post is worrying
Using Google Public DNS fixed things for me.
Earlier quoted context omitted.
I'm so damn tired of the "host it locally" mentality. Not everyone has the resources to host all of that locally. For example, most open source projects. But even outside of that, we use github for issue tracking, the new project management kanban stuff, a CI server, reading documentation (which is offline, but the online versions are nicer on the eyes), and a ton more. Not to mention that StackOverflow and other dis…
And I'm so damn tired of people complaining about cost to run stuff locally. The true cost of not having some basic stuff setup locally, even for backup purposes is when situation like this happens. It does not take long time or resources to download all of the libraries, with corresponding docs to a local server, or even your laptop. It is not complicated to have all of the new issues sent to an email to have a vers…
If self-hosted, somewhere, you could still be screwed by having Dyn as your DNS provider.
If dev-machine-hosted, then uh, your issue tracker is no longer an issue tracker. Your build server is not a build server. All the services besides Git are not meant to operate offline in a decentralized/distributed fashion.
Library documentation, sure, that could be local. Otherwise, your assertion that all of this tools infrastructure can somehow be replicated, easily, in a way that makes the difference between working online or offline effectively zero, is nonsense.
Earlier quoted context omitted.
The zsh default git plugin definitely doesn't touch github, or the network in general. Are you using some oh-my-zsh github plugin by any chance?
plugins=(git rbenv nvm gitfast zsh-autosuggestions github)
https://github.com/robbyrussell/oh-my-zsh/wiki/Plugins#githu...
oh-my-zsh is, imho, way overengineered and bloated. Leads to all sorts of issues like the one you're encountering there.
I would recommend sticking to a plain zshrc file that you can read, edit and fully understand.
The one I wrote and am using day to day is available here, with documentation: https://github.com/jleclanche/dotfiles