yardstick
Joined 10 years ago
Joined 10 years ago
Bottom bit was confusing. Did he actually get hit or was it just a story? I assume the later but you never know these days…
I would let Chainguard deal with the patches post official release like all other unreliable parties.
Calif more than Chainguard, but still Chainguard too.
Calif was obviously twitching to claim credit for their findings, and what I find troubling is this eagerness was more important to them than giving users a chance to update their systems.
Even if they ended up waiting only a day post release I would still say it seems a bit too soon. Maybe a week after. Not everyone’s system have aggressive patching schedules and PHP is soo heavily used.
Plus as per this article, the rider is way less likely to talk important business in front of the driver - hence Waymo being ideal.
That’s about one consent every 26.5 metres. A modern intercity train carriage is about 25 metres long.
It seems like a crazy number of consents for the distance.
Allow git clone for free/unrestricted still.
Require the user to sign in to view html views. Sign in require a valid email or phone where a validation link is sent.
Or: Users signed in won’t see the Anubis. Users not signed in can still see the html views but have to use a very high work level?
Or: Limit unauthenticated requests from an IP to 5/minute. Authenticated requests can do a lot more before hitting the limit.
But you don’t really want lots of idle or underused servers, aside from burst capacity management. So if they universally and consistently wrote more efficient code I’d expect a smaller datacenter. Full of still busy servers but just less of them.