an_account_name

CVE-205BC-00001

Suspect they're talking about Java - a lot of frameworks do exactly create a thread per request.

If they can do a manual review at all, then there isn’t end to end encryption anymore, so I’m missing what the point of client side scanning is.

If it’s in APLCore it’s still running somewhere, you can be sure

I mean out of the Symantec roots...

Ooh, I bet WoSign would do it!

So the mitigation would be to add a check that the generator point in (for example) a CertificateVerify message is the one in the p256 spec (or otherwise the one on the cert, I’m not deep enough to know where it usually lives)?

AWS has a region in Brazil, sa-east-1

As they say it’s not “but”, rather “yes, and” so I agree with that and would add that the likely sentience of whales is a huge factor here.

What was the relative scale of the two systems?

Can you elaborate? I don't have any context on this other than taking a Lyft in NYC once.

!fq cockroaches

No, this absolutely checks with my experience - I chase 5 and 10ms improvements all the time because we've measured and know it increases conversion.

But it makes sense, too: if the metric here is average latency, that doesn't mean that some users didn't see a much more dramatic increase. Every tiny bit of frustration removed from the experience adds up.

Plenty of software runs on platforms other than windows. Plenty of industrial control software, too.