Live data from Hacker News

We are investigating reports of degraded performance

githubstatus.com

121–130 of 152 posts

Re: We are investigating reports of degraded performance

#121

My repos were coming up as 404s. I was wondering if I had been canned...

The "nothing to see here" approach to access control has a lot of weird culture-consequences. I wish software would just address me like the peasant that I am, rather than trying to gaslight me into believing that my artificially limited world is the whole one.

[deleted]

Re: We are investigating reports of degraded performance

#122
post #110
post #96

Earlier quoted context omitted.

So how do you keep data synced between them in a manner that ensures the data is safe? Now you're playing security sysadmin, and you're playing backup administrator, and your playing hardware admin (did you use 2 SSDs bought at the same time?). You don't ever escape the payment cost of the issues of keeping these systems running. You're paying staff to do it, you're paying a cloud provider to do this, or you're payin…

If these things were so insurmountable, the early internet would not have existed at all. Yet it did and still does in many corners, which stands to reason that you can do these things too.

This is where I quote a Narina meme and say "Don't quote the old magic to me..."

You're engaging in survivorship bias. One of my first 'social' media/forum accounts accounts was lost when the admin of the site dropped the user table from a database, and had to go back to everyone online and ask for people to mail in about their accounts. I never bothered to set it back up.

Piles of other smaller sites disappeared for similar reasons. If you completely ignore all that, then yea the old internet was fine. Oh, and that these days hackers are highly motivated to encrypt all your crap for bitcoin.

Typically big sites don't disappear because they depend on separation of duties between different teams doing their responsibilities. For example, knowing how backups work and making sure they are working every day.

Re: We are investigating reports of degraded performance

#123
post #110
post #96

Earlier quoted context omitted.

So how do you keep data synced between them in a manner that ensures the data is safe? Now you're playing security sysadmin, and you're playing backup administrator, and your playing hardware admin (did you use 2 SSDs bought at the same time?). You don't ever escape the payment cost of the issues of keeping these systems running. You're paying staff to do it, you're paying a cloud provider to do this, or you're payin…

If these things were so insurmountable, the early internet would not have existed at all. Yet it did and still does in many corners, which stands to reason that you can do these things too.

It’s not insurmountable, just there’s no point in adding that risk to most projects. Would you rather tell your boss so and so failed because of a news-worthy GitHub incident or so and so failed because all 3 backups of your own DIY service were taken down by some extremely unlikely (but not impossible) chain of events?

Re: We are investigating reports of degraded performance

#124
post #105

Question. Recently github is pushing very agressively for two factor authenticartion. So I installed the authenticator app. But the authenticator does not work when the clock on my phone is not perfectly synchronized. But my phone's clock is intentionally sped up by +15 minutes? What to do?

TOTP usually only allows for about 30 seconds of time drift between the device and the server. If you really must set your phone to the wrong time you can use a cheap second device, or a hardware token.

Technically if an authenticator app has an option for a time offset it should work, but I've never encountered one.

Re: We are investigating reports of degraded performance

#125
post #45
post #27

Earlier quoted context omitted.

It should load faster if there's nothing to load

If nothing loads nothing gets cached and you can get in a cycle of very slow 404s. The current abomination I'm working on avoids this by caching the errors and serving them for several hours...

Is this a designed self-cache poisoning? Abomination indeed.

Re: We are investigating reports of degraded performance

#126
post #93

Earlier quoted context omitted.

Why the downvotes? If you want real security, self-host your Git repo.

I'll bite. So you want to host a git repo. You need to manage SSH keys then, and then you'll want bug tracking and PRs for code reviews. This means that you need to host something like Gitlab, which is not free if you want features like SSO.

Gitea has SSO and is free.

Re: We are investigating reports of degraded performance

#127

Earlier quoted context omitted.

What exactly is the risk? That they'll stop providing the services they sell today? The design of git makes switching to another primary remote very easy (granted, most users probably don't have good habits around backing up data from Issues/Wiki/Releases and risk losing that data if it's taken away suddenly -- but the repo itself is durable and portable on a whim.

You have slightly illustrated it yourself in a roundabout way, but let's be clear with wording here: > The design of git makes switching to another primary remote very easy It is never as easy as just switching to another primary remote. It's not just Issues/Wikis/Releases, but the build/CI process(es) that are rampant on GitHub now, the community you've built potentially coming up on GitHub and not really getting th…

Quick data point: while not exactly trivial, my team has migrated completely from github to our own hosted gitea. Including CI, releases, issues, read-only mirror back to GitHub, PRs etc. The only thing we don't have that would be nice is the ability to take a PR directly from a fork of a repo in someone else's Gitea deployment (or GitHub for that matter). To take an external PR we either need to recreate it manually in our Gitea under a team member's account, or give the external contributor an account on our Gitea.

Re: We are investigating reports of degraded performance

#128
post #105

Question. Recently github is pushing very agressively for two factor authenticartion. So I installed the authenticator app. But the authenticator does not work when the clock on my phone is not perfectly synchronized. But my phone's clock is intentionally sped up by +15 minutes? What to do?

If you can get oathtool from fdroid termux, it can generate a "not-now" TOTP token for you if you still have the OATP parameters.

Re: We are investigating reports of degraded performance

#129
post #118

Earlier quoted context omitted.

Synchronize your clock.

I want my clock to be sped up by 15 minutes.

You could fork some open source TOTP app and change the time generation.

Or you can save your code and wait 15 minutes to login.

Post reply on HN