It should be fairly easy to see statistically if ECC helps, people do run Firefox on it.

The number of bits in registers, busses, cache layers is very small compared to the number in RAM. Obviously they might be hotter or more likely to flip.

I believe caches and maybe registers often have ECC too though I'm sure there are still gaps.

A lot of words to say adding a column to passwd and changing all software that creates accounts will take some work. For me giving parents more tools seems easily worth the work, but I can understand others who disagree.

My React website can't star React on GitHub.

Not with that attitude it can't!

Now I have this terrible idea:

const openClawInstance = useOpenClaw(config);

Did anyone already vibe-code such silliness? If not, I want to give it a try.

I'd love to read about that going super sideways. Bonus points if you run it in a webworker like those crypto miners.

__ but everyone knows about facebook though __

React popularity is also a phenomenon closely tied to popularity of the fb

Maybe for the first 2-3 years. The association to Meta is barely mentioned (even on the official page) nowadays.

My impression is react is almost thought of more as a Vercel project these days

For $2,500 the Carvera Air makes very nice 2 sided pcbs with solder mask. Though even in raw materials it is hard to match a finished board from China if you can wait a couple of months.

In my experience it's a couple of weeks, not months from China.

Depends how much you are happy to pay; but yes it has got faster.

All the law asks is that 'adduser' asks for their birthday; and and age restricted software checks this on installation. Given we already have software it is illegal to sell to children this seems like an easy win? (Obviously it is still down to the parents to ensure the account is setup correctly)

Unrestricted API keys were always secrets. They are created on a page called "Keys & Credentials". The fact that Google even allows unrestricted keys to be created has been a long standing security problem. The fact their docs encouraged it remains unforgivable.

Public keys are a thing in computing, though?

Google Maps has one, even. And Stripe.

It's been a while since I've used stripe but don't their keys start with sk_ for secret and pk_ for public?

I like that. Easy to tell if you should keep the key a secret or not.

They do, yeah.

(Although `pk` always freaks me out. Public or private?! Oh, right, the other one's "secret".)

Or is `sk` shared key and `pk` private key...

OK now I'm rethinking my life

Honestly we should just always call them public and secret key to avoid confusion

I would like to restrict the term "Public keys" to refer to asymmetric encryption keys which can be made public without compromising security.

The only purpose of the keys Maps/Stripe encourage you to publicly put into your website is to guarantee it is talking to _your_ Google/Stripe account not someone else's. Obviously once you put them in your client they are of zero value in helping Google/Stripe identify you. The fact that Google allows you to use the same type of key they also use elsewhere to identify _you_ not _them_ was always incredibly bad design. Google already have the 'Project ID' which would have been the best thing to use.

I can maybe understand unrestricted keys (OK, I can't, to be honest).

But the fact that permissions are not hardened at time of creation is bonkers to me.

I also missread Only as Open

Is the possibility to write an infinite loop in your language of choice a bug?

Most regex usage actually doesnt require near infinite backtracking, so limited unless opted in wouldn’t be that weird.

It only changes the types; not the code.