Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident with Github.com [resolved]

githubstatus.com

Post reply on HN
Print view View original

451–460 of 1001 posts

Re: Incident with Github.com [resolved]

#451

Post by wejick »

I can imagine the massive growth they're in right now, old assumptions are breaking down, many things need to be rethought. That's why personally i don't hate them with all of this saga. But they need to work faster in terms of product decisions and technology.

Re: Incident with Github.com [resolved]

#452

Post by cautiouscat »

stingraycharles wrote: post #52
khvn26 wrote: post #29

I had a lot of goodwill for GitHub but I think today is the tipping point. Looking at a unicorn page, I feel this lingering hope that it's transient (like it usually was in the old days) but my mind reassures me it's probably going to be a long full outage again. The hope is dead.

I’m willing to give them a break as I’m assuming they have a lot of scaling problems due to the influx of LLM assisted coding. But maybe I’m wrong?

That’s the reason they gave, and I believe them. But I also think there has to be more to it. If your paying users are seeing degradation caused by (likely) free tier users (for years by the way), restrict the free users.

Re: Incident with Github.com [resolved]

#454

Post by pigeons »

TZubiri wrote: post #234
AlexandrB wrote: post #167

Earlier quoted context omitted.

Boomer opinion but trusting third parties to be critical infrastructure, especially with no SLA in sight, will always end in tears. "The cloud" is very convenient, but its providers will never care about your infrastructure or your customers as much as you will.

Boomer who has never had a business? Depending on third party suppliers is business as usual.

Well it's not business at all today!

Re: Incident with Github.com [resolved]

#456

Post by klaussilveira »

I encourage everyone to switch to Forgejo. We ditched GitHub and could not be happier. The experience is smoother, faster and distraction-free.

Our runners are faster, our CI is smoother than ever. Transitioning was a matter of a few hours, which we took as a fun hackaton.

Re: Incident with Github.com [resolved]

#457

Post by neuronic »

piker wrote: post #369
imnes wrote: post #286

GitHub, Charles Schwab, Microsoft Teams, Copilot, New York State, AWS, Progressive, Azure, Microsoft Store, Cloudflare, ADP, Google Sheets, E-Trade, Fidelity... Did Mythos break out of it's container? https://downdetector.com/

Maybe it's this one: https://downdetector.com/status/windows-azure/

Because Google Sheets is famously running on Azure?

Re: Incident with Github.com [resolved]

#458

Post by jasongi »

smcameron wrote: post #444

I wonder if you could replace the whole github issues feature with just a directory within each git repo named "Issues/". Within that, have another couple directories, "open/", and "closed/". Within "open", have a directory per issue, e.g. "such-and-such-does-not-work/". Within each issue directory, have "issue.txt", or "issue.md", which takes the place of the page for each issue on github. You could store other thin…

The whole point of issues is that users can create them when they don't have repo write access.
Post reply on HN