rancar2

I’m happy to connect you to others in that specific space that. I’m easy to find by adding a dot com after my username.

There is a liability in the USA if their organization was the one leaking, so plausible denial is the legally safe route to take for a company governed by USA regulations.

It documents that there was active attack four days prior to the embargo with suspected leak happening prior to Pete’s post here on HN, which was a day before the embargo ended that Pete was unaware of when posting.

That is part of the human victory, but there’s still more to be done to close the chapter fully. There is still on-going developments and testing even into the past decade that are publicly known (and more privately known to have leaked) that have follow on effects for all current and future living creatures of Earth. This chapter of humanity is unfortunately still active to the determinant of all.

TLDR: I was called in several hours after the downtime started. I architected and built the full system so I knew things were incredibly consistent and how every layer worked (each layer of the software/database, load balancers, the quirky legacy protocols, network setup, etc). IBM was saying it was an issue on the financial institution side, which I validated was not the case practically first (things were down so I was given freedom by the executive team to do as I needed). Since I sanity checked the easy parts first and had high confidence this was something much more wild after scanning through more stack traces than a human should, I decompiled and reverse engineered their code to show the IBM teams where the bug was in their switch statements triggered by the Redhat patch difference and its dependencies that triggered the edge case that stopped the highly available cluster setup from functioning. I created a script to override the system properties being read in on startup to trick the switch statement, show it worked, and got the system back online. IBM made an official hot patch that fixed the issue officially along with paying a lot of money back to the financial institution for their troubles (ie the double contractual obligations for the premium IBM support with included SLA clauses that were overrun and the proprietary IBM software itself).

I have built these system for financial institutions since before cloud providers. It is hard/impossible if not well constrained at a level that supports data availability and consistency well (ie using a proper database with the correct setup across all locations with the underlying OS configuration/patches applied uniformly - the latter lesson cost IBM a lot of money due to system downtime for a financial institution that I brought back online). Many software vendors offering on-prem versions don’t know how this works well exactly, so I’ve had to help them along the journey and get them to sign-off for their contractual obligations to be upheld in the setup.

I was only encouraging the individual’s good work here vs a lot of the negatively being thrown out. I was noting the rest and not endorsing it. I’ve built payment and billing system at scale in both B2B and B2C contexts. These mistakes would have never been in production and aren’t acceptable from a vendor imo.

Thanks for the attention and fixing this.

Note to others who are blaming Amthropic in various ways. This is what taking responsibility is.

Note also that Anthropic outsources the billing and metered billing to a third party still, who is doing very well with the growth. It’s a more recent company in the space so it comes with a lot of bugs that are getting learned with time which is why there are so many interesting (at scale) and obvious errors (billing systems are build over years not months) being corrected with time.

I think it’s covered appropriately for the audiences. The two posts are for different audiences and purposes. The Deno post by Ryan is for the Deno audience, which is mention at the top of his writing on the Cloudflare post that is for a broader audience of what this means for the Cloudflare audience: “For more on what's happening to the Deno runtime and our various efforts, see my post on the Deno blog.”

FWIW both Ryan and Kenton are very transparent in person, in public, and online over their professional careers. They will and do openly change their minds based on new information and opportunities as time goes along. Both are now founders of open source projects acquired by Cloudflare for the technical architecture talents seeing a future that they would like to build.

The videos of the features are very well done, and it looks like there is a unified vision, which is not what any of the other products have. Did Google copy some of the UI/UX? I was curious where their inspirations were, and I think this may have been it.

I look forward to the beta and beyond!