Agreed, and there is already a solution that’s better to support anyway. It may not be perfect, but Wikipedia operates on this model at scale at a much smaller annual budget than any of the AI companies and has produced much higher quality content overtime for all of humanities benefit than the AI teams which are most just scraping the work of others while spending most of their original work to replace human labor for their own financial benefit.

Wikipedia community bans AI-generated entries because verifying and removing AI hallucinations imposes even more workload on editors than writing articles from scratch [1, 2].

If you don’t agree that Wikipedia’s approach, one can always fork it like was done with SpaceX / Twitter did with its launch of Grokipedia on October 27, 2025, which hasn’t been really incorporating much improvement well with lots of digressions in its quality and reliability [3].

[1] https://en.wikipedia.org/wiki/Wikipedia:Writing_articles_wit...

[2] https://en.wikipedia.org/wiki/Wikipedia:Editing_policy#Artif...

[3] https://en.wikipedia.org/wiki/Grokipedia#Reliability

[Edited for better formatting]

Andrew, congrats on the launch! Great to see another scaled manufacturer and assembly line here in Massachusetts. I helped scale another startup with personalized for 3D prints for orthodontic braces (https://lf.co/blog/deloitte-fast500-2024), so feel to reach out to exchange tips since the generic mass manufacturing world is not well suited for this new world of “one size fits one” at a global scale.

Also, one question to pick your team’s brain: What’s your team’s AI PCB workflow and design tips to work with your production line? Any specific tips for ESP32-related integrations?

Thanks, that sounds like an interesting project! We are starting to see a few AI designed boards flow in and we're working on some guidelines, should be coming soon!

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.

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.

That’s kind of you, Pete, but it was leaked and being exploited well prior to your previous posting here: https://aws.amazon.com/blogs/security/amazon-threat-intellig...

No leak claimed there.

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.

The vulnerability could have been independently discovered. Organizations involved have said that's not unlikely

"it remains unclear how the actor acquired exploit information prior to disclosure."

Technically true, but also not important.

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.

> the latter lesson cost IBM a lot of money due to system downtime for a financial institution that I brought back online

It sounds like that story could make a great blog post

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).

The readme links to the paper (in the badges), which is more helpful in understanding the project: https://arxiv.org/pdf/2610.14224

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.

Unless they are changing their support process to not require a user to post on a message board and hope a developer sees it, I don't see how it's really taking responsibility.

And why should I give them more leeway for outsourcing to an inexperienced company? Comma/decimals meaning in currency is pretty well-established. If a new company is moving into an established space I would expect them to learn from other folks past experiences. "whoopsy, we don't know our core competency" isn't a defense for a company that's presumably making exorbitant amounts of money from partnering with Anthropic.

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

It is way too early to tell if Anthropic is "taking responsibilty" for this. I'll be awaiting the news that they started aggressively hiring human support staff to field user complaints so they don't continue to do shit like this. That is taking responsibilty.

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.

There's no need to excuse this behavior. People who write announcements like this are dishonest to their core.

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!

Great questions. We are incredibly far off in understanding the brain of humans beyond what will I believe we retrospectively be seen as basic and will likely be seen as quite flawed. A few more well known examples of where knowledge already falls short is traumatic brain injuries that are diagnosed in post-mortem, or chronic fatigue symptoms (with Long Covid related triggered onset and numerous others) that have diagnostic challenges, many mechanisms of action still to be discoverd, and little in terms of treatments that provide known cures without experimentation. Another commonly known one is the personal patient response and triggered side effects of SSRIs and SNRIs. If one attempts to dig deeper into where we are at in the understanding of the human brain operation in real-time, we already have a lot of knowns unknowns and discoveries left that will reshape how we model human intelligence.