From the blog you quoted yourself:

Despite improving AI energy efficiency, total energy consumption is likely to increase because of the massive increase in usage. A large portion of the increase in energy consumption between 2024 to 2023 is attributed to AI-related servers. Their usage grew from 2 TWh in 2017 to 40 TWh in 2023. This is a big driver behind the projected scenarios for total US energy consumption, ranging from 325 to 580 TWh (6.7% to 12% of total electricity consumption) in the US by 2028.

(And likewise, the last graph of predictions for 2028)

From a quick read of that source, it is unclear to me if it factors in the electricity cost of training the models. It seems to me that it doesn’t.

I found more information here: https://www.technologyreview.com/2025/05/20/1116327/ai-energy-usage-climate-footprint-big-tech/

Racks of servers hum along for months, ingesting training data, crunching numbers, and performing computations. This is a time-consuming and expensive process—it’s estimated that training OpenAI’s GPT-4 took over $100 million and consumed 50 gigawatt-hours of energy, enough to power San Francisco for three days.

So, I’m not sure if those numbers for 2023 paint the full picture. And adoption of AI-powered tools was definitely not as high in 2023 as it is nowadays. So I wouldn’t be surprised if those numbers were much higher than the reported 22.7% of the total server power usage in the US.

Not even remotely close to this scale… At most you could compare the energy usage to the miners in the crypto craze, but I’m pretty sure that even that is just a tiny fraction of what’s going on right now.

Or use yEnc: https://en.m.wikipedia.org/wiki/YEnc

Hate speech is not “saying that you hate something”…

https://youtu.be/4IIVfoDuVIw

The downvotes are just typical Reddit/Lemmy superiority complex, whenever some science stuff that “most people don’t know” shows up, anyone saying anything different gets downvoted a ton.

Source/opinion/joke, doesn’t matter, just going against the hivemind.

What about the videos recorded in Ecuador, where the same reservoir is drained on both sides of the equator and the water spins in different directions?

Edited to add the link since other users asked for it down in the replies: https://youtu.be/4IIVfoDuVIw

Edit2: check the replies below, the video is good at debunking this. But it’s not super easy to notice

The meme is not about the miscarriage but about how tone deaf it was. So your point is actually why the meme started being a thing, mocking the comic itself. That’s the context of it as far as I’m aware

It’s my belief that it’s rare for evolution to screw up.

That’s not how it works, I’m pretty sure… Mutations will have random effects and the species evolves based on characteristics being selected for based on better survivability, reproductive effectiveness, etc.

I would do everything I could to find an alternative solution and talk them down from it.

I’ve read your other messages and it seems that you’re thoroughly convinced that this wasn’t the case here. I suggest that you get a bit more context about this whole situation, as it has been a long path of trying multiple treatments and approaches, without any success. So it’s not even remotely close to what you suggest here. No Futurama suicide chambers here.

Do people know you’re circumcised based on your skin colour? Seems like a facetious comparison

I’m pretty sure that this is not true. I’d love to see sources.

There was some research before the ongoing AI-panic, focusing on hentai instead. As it is as “harmless” as the AI-generated content.

And I do recall that at the time there were voices in research making the point that the consumption of material did not have correlation with actually reducing the urges. So this seems highly unlikely.

Just use the icon from the streak society…

Wait, you’re not AI too?

Shared branches should always only move forward. Most Git-* systems support stuff like protected branches.

I personally like tidying up your own feature branch with rebasing and then merging it into main (preferably using only FF merges). However this is not scalable for some larger projects, and for example monorepos also make this hard to accomplish. In those cases the solution ends up being squash+merge.

The extra information about the squashed commits is usually persisted to these systems (GitHub PRs, GitLab MRs, etc) so you don’t really lose much, I guess. Although I do prefer keeping it all in plain git.