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

Authentication issues related to API requests

githubstatus.com

Post reply on HN
Print view View original

21–30 of 36 posts

Re: Authentication issues related to API requests

#22

Post by lenerdenator »

Madmallard wrote: post #20

Why are they even changing GitHub? Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?

Line must go up. They're already the default choice for hosting software repos online, so it's time to look at the next thing, whether that be CI/CD or AI or whatever.

If line doesn't go up, some Ivy League business school grad who has holdings in MS might make slightly less money and have to cut back on the nose candy budget while summering in the south of France this year.

And that's just inexcusable.

Re: Authentication issues related to API requests

#24

Post by Traubenfuchs »

Madmallard wrote: post #20

Why are they even changing GitHub? Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?

There is ALWAYS a need to scale up, upgrade versions, migrate from one database or scheme to another, cut services into more microservices, melt them back into a monolith, integrate more stuff, deprecate other stuff, fix bugs, increase performance, tune caches…

Some things happen for reasons that make sense, others are done for the sake of it. The PO‘s of front end features need to evolve them. What do you do with a PO who says this is done? They don‘t have visibility, don’t get promoted and they don‘t get a bonus. We have created a dashboard that shows that A/B tested users like the new design more by 7%! The next redesign is already planned!

Re: Authentication issues related to API requests

#25

Post by dreday »

Madmallard wrote: post #20

Why are they even changing GitHub? Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?

Because of vibe coding everyone is a developer now so the number of accounts, PRs, repos, etc just 10x'd.

Re: Authentication issues related to API requests

#28

Post by alemanek »

baq wrote: post #12
rvz wrote: post #10

Again? Last time an incident happened was 48 hours ago [0]. Now the API is having issues. Something every week is falling apart at GitHub and it is slowly self-destructing. Each time there is an incident at GitHub, it is another advertisement to self-host your own. Otherwise just expect GitHub to break next week or two. Remember, there is no CEO of GitHub; only their AI agents running it into the ground. [0] https://…

OpenAI, Anthropic and Google serve models, but approximately all of their combined output ends up on github.

They need to split paying customers off onto dedicated infrastructure. I know that you get that with some enterprise offerings but I don’t believe the normal paying customers get that treatment.

It’s clear they have massive scaling challenges but to not tier or isolate your paying customers from the free plan users seems a bit odd. Just my 2cents though.

Re: Authentication issues related to API requests

#30

Post by CamouflagedKiwi »

Madmallard wrote: post #20

Why are they even changing GitHub? Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?

They've been moving it to Azure, presumably partly because they don't want to pay AWS for a thing they could (apparently) do, but more for the appearance of the thing.

I think that's financially sensible in the long run, assuming they believe they can run the thing basically as well on Azure, and aren't expecting major issues during the migration. These have turned out not to be good assumptions.

Post reply on HN