Do we really need to be notified every time GitHub or Twitter go down temporarily? It's inconsequential in the grand scheme of things.
Maybe it's a sign someone should look into an expanded notification system. I imagine someone could cook up an interesting IF case for IFTTT. A good way for a company like GitHub to do it might be an RSS feed. That won't necessarily allow to define a status message type indicating the occurrence of the problem vs. the resolution - and the severity of the status problem.
GitHub was experiencing a DDoS
71–74 of 74 posts
Re: GitHub was experiencing a DDoS
#72Earlier quoted context omitted.
Maybe it's a sign someone should look into an expanded notification system. I imagine someone could cook up an interesting IF case for IFTTT. A good way for a company like GitHub to do it might be an RSS feed. That won't necessarily allow to define a status message type indicating the occurrence of the problem vs. the resolution - and the severity of the status problem.
The do have the linked website (status.github.com) and a twitter account (@githubstatus) which honestly seem pretty sufficient already.
(note that I'm not agreeing we should post to HN for every blip)
Re: GitHub was experiencing a DDoS
#73Earlier quoted context omitted.
Just have both gitlab and github as upstreams and push to both every time. aka in your .git/config: [remote "origin"] url = https://github.com/somerepo.git url = https://gitlab.yourdomain.tld/somerepo.git fetch = +refs/heads/*:refs/remotes/origin/* And nothing to worry about when github is down.
Huh. I wasn't aware you could do that. What happens if the repos aren't in sync and you pull?
Re: GitHub was experiencing a DDoS
#74Who would do something like this?