Here’s the email to employees:
Team,
Hope everyone’s doing well and enjoying the productivity enhancements from our AI tooling initiative.
Unfortunately, Finance has asked me to clarify a small issue.
It appears someone, and by “someone” I mean apparently all of you simultaneously, managed to spend $500,000,000 on @claudeai usage in a single month.
For context:
•NASA landed on the moon for less.
•We are now the proud owner of approximately 14% of Anthropic.
•Claude personally sent us a thank-you fruit basket.
•Our CFO has entered a fugue state and only communicates through Slack emojis.
•The electricity usage from your prompts briefly dimmed parts of Northern Virginia.
While we appreciate innovation, there are concerns that:
•“Can you make this email sound slightly warmer?” did not require 11,400 generations.
•Asking Claude to “rewrite this in the style of Succession, Hemingway, and Tony Soprano combined” may have been excessive.
•One employee appears to have used Claude to generate “a quick list of lunch options” that somehow consumed the GDP of a small island nation.
Going forward, please observe the following guidelines:
1Do not upload the entire internet into Claude “for context.”
2If your prompt begins with “simulate every possible outcome,” reconsider.
3Claude should not be used to:
◦settle fantasy football disputes,
◦write your wedding vows 97 times,
◦generate revenge edits of your ex’s LinkedIn bio,
◦or ask “what if Rome had WiFi?”
Most importantly:
If you see the message:
“This request may require additional datacenter construction”
…please stop immediately and contact IT.
Thank you all for your cooperation during this challenging yet technologically groundbreaking time.
Warm regards, Management
P.S. Whoever prompted:
“Generate every possible PR angle for every company founded since 1983”
…we just want to talk.
Introducing Trusted Remote Execution — an open source scripting runtime built on a simple rule: no operation executes without explicit policy authorization.
• Rhai scripts: sandboxed, no built-in host access
• Cedar policies: declarative rules for what's allowed
• Same enforcement for human-triggered and AI-triggered scripts
https://t.co/0fN9c2L7EJ
#OpenSource #Security #AWS
We hacked the AWS JavaScript SDK, a core library powering the entire @AWScloud ecosystem - including the AWS Console itself 🤯
How did we do it? Just two missing characters was all it took.
This is the story of #CodeBreach 🧵👇
He writes:
> When you are paying by the "pull of the handle," the vendor's incentive is not to solve your problem with a single pull, but to give the appearance of progress towards solving your problem.
https://t.co/CWHE7kaP6x
22/
Tried https://t.co/YanEAfcHuF, #claude-4-opus-thinking & occasional human loop-slaying. IJ = #MCP server now, Claude Desktop runs IJ scripts + shows ASTs. Human devs: still in ∃!mode... for now ^^
After much hacking, IJ now has an interpreter written in IJ that self-transpiles to Go. It bootstraps, kinda works. Mission accomplished. Project gloriously abandoned. Like all legendary side quests, it ends in obscurity https://t.co/a9HwmWd2vc
A silly vacation: inventing a scripting language, writing its interpreter in itself, and learning how LLMs & vibe-coding IDEs can help. TL;DR: Programmers still needed (for now). https://t.co/0HbcFnDgD0 #Cursor#Claude#OpenAI
I mean, let’s be honest—every channel is either already drowning in AI-generated content or gearing up for the flood.
So, to really underline that point, here’s a bit of not-all-that-funny, Saturday Developers “Fun”
Enjoy. Or don’t ;-) https://t.co/27SPojUJG9
Ab und zu werde ich gefragt, was ich von der Cybercrime Convention halte.Ich schließe mich da inhaltlich der Einschätzung des CCC vollumfänglich an.Alleine dass das Abkommen zu Cybercrime von Russland vorgeschlagen wurde, die praktisch alle… https://t.co/jqutHDQHF9
After years of research I have finally compiled the complete list of all #IPv4 addresses of all #threat actors: please add 0.0.0.0/0 to your firewall ingress BLOCK rules and you will never be attacked again!