tony-vlcek

The link now returns 404.

Here's one that works (for now): https://github.com/chatgptprojects/claude-code/blob/642c7f94...

Well, even though electricity is a commodity it still needs to be bought. My point is that people funding this will run out of patience paying for the electricity long before the public/regulators will need to step in a decided how much of it you can buy.

I guess you could always just use a fraction of the billions in investments and whip up a few new power plants. [1]

[1] https://www.bbc.com/news/articles/cx25v2d7zexo

Reminds me of an interview with Kyle Fish on 80k hours [1], where he talks about his research and how when models talk to each other:

> [...] something consistently strange: the models immediately begin discussing their own consciousness before spiraling into increasingly euphoric philosophical dialogue that ends in apparent meditative bliss.

Keen to see if that happens here.

[1]: https://80000hours.org/podcast/episodes/kyle-fish-ai-welfare...

> We will quickly lose even the social permission to take something like energy [...]

A way to drum up sense of urgency without mentioning that it's the patience of the investors (and _not_ the public) that will be the limiting factor here?

As an avid user of malinator.com I really like this. mailinator started being recognised and rejected in many forms. Maybe there's something you can do to get ahead of this? Maybe being able to generate random 1st level domain or pick from a large list could go a long way?

Also 2, as part of migrations:

There 3 types of migration files/scripts: structure, basic-data, dummy-data.

structure - new table, add column goes here basic-data - e.g. default config values go here dummy-data - gets used on local and stating

Run migrations with a flag to include the dummy-data migrations.

If the bottom line are donations - as the article states - why push for getting AI companies to link people to Wikipedia instead of pushing for the companies to donate?

Literally the first sub-section of the article:

> At its core, GitOps is simple. You write down how you want the system to look in code and a bot makes the world match that. Your infrastructure lives in Git. You deploy by committing. You roll back by reverting. The robots take it from there.

Logseq user here with an upvote.