Live data from Hacker News

The August 17 outage

github.blog

681–690 of 804 posts

Re: The August 17 outage

#681
post #326

Earlier quoted context omitted.

Why would any company want coding data now? It's all garbage. I'd be surprised if anything past 2025 is even used for training.

Me personally, I would like to own the world's code. The richest man in the world is interested in this dataset as well.

There's nothing special about code here - if you can own the world's $X for any X, you win capitalism.

Re: The August 17 outage

#682
post #141

Earlier quoted context omitted.

wow. they should really institute a maximum amount of individual pushes per-month per-user.

I still remember when they decided to limit the number of private repos you could have as a free user. Kind of silly to me at the time, and even more so now!

I don't think it's silly for free users to be restricted. If you want something, pay for it. Free trials are trials.

Re: The August 17 outage

#683
post #73

Earlier quoted context omitted.

wow. they should really institute a maximum amount of individual pushes per-month per-user.

Which will just increase the cries of "enshittification" and hasten the mass migration to the next free platform that surely, this time, won't ever go down.

Ironically a bunch of people already migrated to Codeberg and then Codeberg announced "heads up, we actually don't want your AI slop, we're for real projects only" and AI coders threw a shitfit on HN.

Re: The August 17 outage

#685
post #350

Earlier quoted context omitted.

Agree - this reminds me very much of the old joke of two economists increasing GDP by taking turns giving the same 200usd back and forth for having each other eat shit. Useful / impressive for whom is the question. Not for us! We pay for Github enterprise, and because GH can't be bothered to separate service tiers for sloplords and actual paying customers we get garbage level performance. They could of course always…

Should use on premises.

Should use Forgejo

Re: The August 17 outage

#686

Earlier quoted context omitted.

When a service that was already the primary git hosting provider for most of the world for 20 years grows at that rate its not mundane and its not comparable to any example.

AWS saw this growth every year for two decades, hyper growth tech sees it all the time

AWS saw doubling in usage every month for 240 months? So it now exceeds the number of atoms in the universe?

Re: The August 17 outage

#687
post #621

Earlier quoted context omitted.

The environmental impact is anything but moderate and the benefits are not obviously tremendous at all. I'm happy using Claude Code as much as the next guy, but saying that the impact has been "tremendous" is vastly overstating the actual results.

I disagree, with the projected doubling by 2030 we're looking at 3% of global electricity consumption or 3.4 EJ, less than 1% of final energy consumption. That is moderate. Energy-intensive industry is around 130 EJ, and global final energy consumption > 450 EJ. Existing documented applications of today's AI have the potential to decrease energy consumption by >13 EJ/year by 2035. Now that was about operational energ…

"Global data centers consumed around 415 terawatt-hours (TWh) of electricity—about 1.5% of the world's total electricity—with AI acting as a primary accelerator for new power demand."

https://www.iea.org/reports/energy-and-ai/energy-demand-from...

That is today where we already consume too much. If by 2030 AI's consumption doubles it gets worse. While training large models draws major initial power, everyday AI usage (inference) now drives roughly 80% to 90% of cumulative AI energy

"Existing documented applications of today's AI have the potential to decrease energy consumption by >13 EJ/year by 2035."

Seems like AI helps slowing down the rise of energy consumption.

We are at a point where we want less CO2 not moderataly more. In the end more is more.

If your doctor tells you to lose weight or you get sick it's not a success to gain weigth slower

Re: The August 17 outage

#688

Earlier quoted context omitted.

Conversely, what suggests GitHub has a huge operating cost? Running a GitHub clone at their same scale as a customer on cloud pricing would likely be insane. But y’all know infra is actually quite cheap when you run it yourself right? It’s usually the case with these M&A deals that the profit just never quite makes sense to justify the purchase price, unless you can truly scale up the user base or revenue model. GitH…

It used to be, and buying a few servers was a cheap way to get off the cloud (if you can manage them efficiently). But with RAM and other costs these days... I've had to rethink it a lot.

It's at worst ten times as expensive as it should be. But AWS was already ten to a hundred times as expensive, so even in the computer parts crisis, self hosting is still ahead.

Re: The August 17 outage

#689
post #174
post #78

Everyone suggesting that they simply charge users for commits to drive off AI-heavy users forgets that Github is owned by Microsoft, who has a big incentive to keep having developers use AI. I suspect that Microsoft would even prefer to have Github operate at a loss, if that loss were because all its users were using their models and paying for OpenAI subscriptions to generate the code.

Microsoft has a financial incentive to push LLMs and also an existential reason since LLM-generated code is incompatible with the GPL.

The GPL is irrelevant nowadays anyway since everything is MIT (corporations won the license propaganda war). I think my computer has, like, five GPL programs? Ten? It's just that two of them are coreutils and Linux, and that basically holds up the GPL as a concept.

Re: The August 17 outage

#690
post #441

Earlier quoted context omitted.

It's AI all the way down. An issue reported by a person account but post made by AI. https://github.com/oven-sh/bun/issues/39800 AI (robobun) responds and creates PR. https://github.com/oven-sh/bun/pull/37459 AI (coderabbit, claude, github actions) review the PR, AI (robobun) applies the fixes. Some AI back and forth. A human finally merges the PR. Not gonna lie, it's kind of beautiful.

Some guy, profiling his linux distro, wonders why ssh connections are a few hundred milliseconds slower than expected, finds there PR introduced and RCE backdoor and p0wns the whole project.

Seriously, this is driving me insane. The XZ hack told us what we had to do to secure our supply chain, and instead we went ahead and implemented a worldwide standard for NLP-to-action and figured we'd worry about the guardrails later. Mad.
Post reply on HN