0 Followers
0 Following
15 Posts
Hacker and (non-practicing) attorney.

Nothing I say should be construed as legal advice. I encourage you to seek licensed counsel in your jurisdiction if you need legal advice.

[ my public key: https://keybase.io/otterley; my proof: https://keybase.io/otterley/sigs/ciQxqIniqjt0qP_lKGryssgeBpYEjANIzawbvj_1Yt4 ]
This account is a replica from Hacker News. Its author can't see your replies. If you find this service useful, please consider supporting us via our Patreon.

Officialhttps://
Support this servicehttps://www.patreon.com/birddotmakeup

DC power has been an option for datacenter equipment since I was a young lad racking and stacking hardware. Cisco, Dell, HPE, IBM, and countless others all had DC supply options. Same with PDUs. What’s old is new again.

See e.g. https://www.dell.com/support/kbdoc/en-us/000221234/wiring-in...

PowerEdge: Wiring instructions for a DC power supply unit | Dell US

This article provides some checklist to prevent unnecessary components replacement on DC power supply implementation.

In theory, yes, but you can't squeeze blood from a stone.
Until someone rich and powerful gets ripped off -- then, suddenly, lots of people care a lot.
*Actual fun may vary.

It helped that, at the time, most video was broadcast over the air and thus subject to FCC regulations relating to content, and that advertisers would pull funds from stations and networks that aired content that was too controversial. Other, non-regulated or less regulated (“adult”) content was for pay and the systems had child lockouts.

It’s much easier to relinquish parental control of media exposure when the system helps you out by moderating the content. But the Internet changed everything. I can’t imagine how difficult it must be as a parent to oversee media exposure for their children nowadays without pulling the plug on social media altogether.

Suppose they did have the cellular architecture today, but every other fact was identical. They'd still have suffered the failure! But it would have been contained, and the damage would have been far less.

Fires happen every day. Smoke alarms go off, firefighters get called in, incident response is exercised, and lessons from the situation are learned (with resulting updates to the fire and building codes).

Yet even though this happens, entire cities almost never burn down anymore. And we want to keep it that way.

As Cook points out, "Safety is a characteristic of systems and not of their components."

It's great that you're working on regionalization. Yes, it is hard, but 100x harder if you don't start with cellular design in mind. And as I said in the root of the thread, this is a sign that CloudFlare needs to invest in it just like you have been.
Have a link?
Those aren't the facts before us. Also, CRUD operations relating to a specific customer or user tend not to cause the sort of widespread incidents we saw today.

If they're going to yeet configs into production, they ought to at least have plenty of mitigation mechanisms, including canary deployments and fault isolation boundaries. This was my primary point at the root of this thread.

And I hope fly.io has these mechanisms as well :-)