Live data from Hacker News

We are investigating reports of degraded performance

githubstatus.com

41–50 of 152 posts

Re: We are investigating reports of degraded performance

#41

Earlier quoted context omitted.

If only there was a decentralized system to allow version management of code.

I realize you're talking about git, but I think it's also pretty important to have a place where users can submit issues and dev's can say "it's fixed in version XYZ", these are not features of git. I've been meaning to give radicle a try.

[flagged]

Re: We are investigating reports of degraded performance

#42

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.

Re: We are investigating reports of degraded performance

#43

I need a macro template for those memes with Bart Simpson on the blackboard and make it say "I will always have a backup plan for third-party services". Seriously people: gitea exists. Gitlab self-hosted exists. Drone/Woodpecker CI exists. It's not that difficult to set up a project that does not depend on Github. I spent less time setting these up than the amount of down time that Github has had this year.

Problem is, this is one of 50 things that can go wrong for which you should have a robust backup plan for

Re: We are investigating reports of degraded performance

#44

Earlier quoted context omitted.

If only there was a decentralized system to allow version management of code.

I realize you're talking about git, but I think it's also pretty important to have a place where users can submit issues and dev's can say "it's fixed in version XYZ", these are not features of git. I've been meaning to give radicle a try.

Fossil does this within the repo, maybe we need a way for Git to do so too.

Re: We are investigating reports of degraded performance

#45
post #27

I like how "Every request returns a 404" == "degraded performance"

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...

Re: We are investigating reports of degraded performance

#46

I cannot wait for Gitea, Forgejo, and GitLab to start federating with each other via ActivityPub. Then we can all take one more step away from a corporate-controlled internet.

That would surely be nice and helpful, but why do we need to wait for it?

Even my open source projects in github are just mirrors from the "real place" of work: gitlab or my own gitea instance. If github is down, it is a minor inconvenience but I can still work.

Re: We are investigating reports of degraded performance

#47

I cannot wait for Gitea, Forgejo, and GitLab to start federating with each other via ActivityPub. Then we can all take one more step away from a corporate-controlled internet.

I'm a little confused, Gitlab is a publically traded corporation?

https://www.google.com/finance/quote/GTLB:NASDAQ

Re: We are investigating reports of degraded performance

#48

I cannot wait for Gitea, Forgejo, and GitLab to start federating with each other via ActivityPub. Then we can all take one more step away from a corporate-controlled internet.

- 'one more step away from a corporate-controlled internet"

Downvote me to grey-world if you like, but I think everyone's crazy to put all their code infrastructure in the hands of fucking Microsoft. Especially literal free open-source software. Who do you think Microsoft is? What do you know of Microsoft's history and their core values (they're "embrace, extinguish & exsanguinate"). It's like giving fucking Sauron safekeeping of your power-rings in Mordor, oh we have great infrastructure for safe ring storage here, very secure, the orcs are really expert guards.

Re: We are investigating reports of degraded performance

#50
post #39

PR really spun gold when they decided to label everything from every single one of their databases getting deleted and backups nuked to intermittent connectivity issues as "degraded". Who exactly are they making feel better by not calling a spade a spade?

People will take issue with any wording. Why try to find the exact right words each time when people will have exactly the same complaints?

I take issue with clear PR-speak trying to make the issue lesser than it actually is. When you're having an outage- call it an outage. Having a feature completely unusable and labeling it as "degraded performance" is clearly twisting your words to lessen the outwardly perception of the scale of the problem.
Post reply on HN