@musalbas

Hey all, thank you for your interest. We've had a lot more interest than we anticipated! We’ve updated the form so you can submit your email address. Please go back to your application and add it as soon as possible! This will make it easier to contact all of you.

I'm looking to build the initial community for a cool and exciting AI experiment built on Celestia. Fill out the form below if you're interested!

👀

Reminds me of the time when a UK law firm didn't realise that IP addresses in the UK were dynamic, not static, so they sent gay porn piracy demand letters to random people https://t.co/8EcatmjwuN

PSA: vibe coding can mass produce CVEs I had Claude Code build and deploy a Next.js app on an isolated VM. pnpm resolved to 15.5.12 - patched against the React2Shell RCE (CVSS 10.0). Build failed. So Claude downgraded to next@15.1.0. pnpm printed "WARN deprecated". Claude ignored it and deployed to a public IP. 51 minutes later: cryptominer. One unauthenticated HTTP request via CVE-2025-66478 gave the attacker full RCE inside the Next.js process. The miner ran from memory, installed 4 persistence mechanisms in under a second. The secure version was already installed. The AI chose the vulnerable one because it made the build pass. No harm done - this was a throwaway VM. But imagine this on real infrastructure. AI will always choose working over secure. Review your deps before deploying.