dpe82

I don't really understand the controversy; there are plenty of licenses an author can choose that restricts commercial use of a project. It feels a bit dishonest to release something under a permissive license and then be upset when someone uses your stuff well within the ways you said is perfectly ok.

  YOU> hey
  C64> HELLO! RE SOUNDS ME. MEFUL!

60s per token for that doesn't strike me as genuinely useful.

Very, very cool project though!

Let's be generous and pretend the rest of the hardware is free but double the energy budget of the H100 to account for all of it along with cooling. You're still at only $1k/yr; $10k over 10 years, or 25% of the TCO (ignoring all other costs).

Power is not the most expensive part of data center lifetime cost; especially these days when you're filling them with several billion dollars of nvidia chips. It's still an important consideration of course, but not the only one.

Yeah that was my second thought. ECS' favoring of structs-of-arrays over traditional arrays-of-structs for game entities boils down to the same motivations and resulting physical layout as column-stores vs row-stores.

This seems cool but man it's hard to get over the very, very obvious AI writing.

None. The magic is still in the model.

How about we legalize construction of new power sources and let the market figure it out?

My very fuzzy back of the envelope says easily 10s of thousands per day.

Genuinely curious: if you just need an independent audit report to check a box, do you really care how good a job the auditor did?

Old men yelling at the sky don't often seek rationality or nuance in their cries.

Google explicitly allows third party email clients to work with Gmail, so no that hypothetical does not apply to this situation at all.

By adding a simple birthdate field to your account info and a system API of some sort for retrieving the account owner's age range, same as everyone else.

The power and importance of marketing is deeply underappreciated by us technical types.

It's certainly better than nothing. Hence "probably doesn't matter too much in this context" - but of course it always matters what your threat model is. Your own agents under your control with aligned models and not interacting with attacker data? Should be fine.

But too many people just automatically equate docker with strong secure isolation and... well, it can be, sometimes, depending a hundred other variables. Thus the reminder; to foster conversations like this.

Nitpick, which probably doesn't matter too much in this context but is always good to remember: Docker containers are not security boundaries.

Usually I'd just look at clusters of crashes (those that had similar stack traces) but sometimes when you're running a very small % experiment there's not enough signal so you end up looking at everything. And oh boy was there a lot of noise.

In an app with >billion users you get all kinds of wild stuff.

It doesn't even need to be that complicated. OS asks you your birthday at setup time. Stores it. Later, an app asks whether the user falls into one of the following brackets:

A) under 13 years of age, or B) at least 13 years of age and under 16 years of age, or C) at least 16 years of age and under 18 years of age or D) at least 18 years of age.

that's it. The OS can decide how it wants to implement that, but personally I'd literally just do get_age_bracket_enum(now() - get_user_birthday());

The bill is here: https://leginfo.legislature.ca.gov/faces/billTextClient.xhtm...

The uproar seems to be extremely overblown.

I'm probably missing something, but when I read the California statute I didn't understand it to be anything like "computers enforcing age" - more like, when you create an account it needs to ask your age, and then provide a system API by which apps can ask what bracket the account holder is in. This seems better than the current solution of every app asking independently?

Again, I'm probably missing something but it strikes me as pretty trivial to comply with?

Oh this is timed perfectly - I was just writing my own erlang agent framework but this is much better!

As a mobile dev at YouTube I'd periodically scroll through crash reports associated with code I owned and the long tail/non-clustered stuff usually just made absolutely no sense and I always assumed at least some of it was random bit flips, dodgy hardware, etc.

I assume you're doing things with the API that aren't coding tasks that could be done with Claude Code? Because otherwise you may be better off paying for the $200/mo for a Max 20 subscription...

2. fun

ZFS snapshots can be used to similar effect, basically for free.

Kagi assistant includes all Anthropic, Google, OpenAI and Grok models as well as all the common open weights models.

The act doesn't explicitly require watermarking, does it?

Even better is the live version: https://vimeo.com/714215610

To each their own.

Sonnet 4.5 was a pretty significant improvement over Opus 4.