Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.

reverse engineered Netflix last night, canceled my subscription, re-subscribed this morning

5 automations every service business should have before hiring another person: 1. every missed call gets a text back within a minute 2. every new lead gets a reply in 60 seconds, day or night 3. every quote gets followed up on day 1, 3 and 7 4. every unpaid invoice gets a reminder before you have to ask 5. every finished job asks for a review the same day hire for judgment. automate the rest.

Zapier is an official @SpaceXSI launch partner. Just tell Grok Bot what you want to build. Instant access to 9,000+ apps through @Zapier. Grok Bot can build automations, and Zapier hosts them. Each one runs on a trigger, deterministically (the same steps every time), so it's faster and costs less than having AI do the work on every run. @ckor showed the team an example: @Bot set up a Zap on its own for a job that ran on every new email. Without Zapier, Grok Bot would have had AI check his inbox constantly. But the Zap, an automation, only runs when a new email shows up. Grok Bot picked the cheaper path. Connect Zapier once and your agent can work in the tools your company runs on. That's 30,000+ actions it can take without connecting each app one by one or building an integration. Companies need rules before handing personal agents real work. With Zapier, admins pick which apps and actions each team can use. Just send this post to your Grok Bot and tell it to install Zapier.

Who will win? @claudeai @bot @Meta @OpenAI

we did invent it and it's called OIDC federation vercel and github actions do it: - each deploy gets a short-lived signed token - AWS/npm/other services verify it via trust policy - you get temporary creds no keys to paste the problem is not enough APIs and services accept it

your coding agent has tried to fix the same thing five times. now something else is broken, and you’re losing track of what it’s changing. stop letting it dig. when something works, save a checkpoint in git. give yourself a version you can return to instead of hoping the next attempt fixes everything. before you try again, ask: “how can we make this smaller? what’s the first change we can verify?” understand what that step should do. check that it works before adding the next one. there’s a reason engineers try to keep pull requests small. smaller changes are easier to understand, check, and recover from. that matters even more when you’re still learning.

Introducing tsrs: a Rust port of the TypeScript compiler 🦀 We are not forking TypeScript! ◆ In close collaborating with the TypeScript team ◆ Up to 8x faster than TS 7.0 & ~70% less memory ◆ Runs in WASM, so it works in your browser & on Workers ◆ Soon part of the Oxc toolchain npx tsrs blog.cloudflare.com/typescri…

1/ Introducing the Cua Spaces SDK. Every big lab now ships a bot with its own computer: Grok Bot, Muse, dots. None let you bring your own. With Cua Spaces, now you can. Put Claude Code, Codex or any agent on compute you choose, and run jobs across all your computers at once.

Day 16/ You can now cache for 12h in the API and for logged in users across Codex & Work we keep cache forever and you don’t have any penalty for coming back to an old conversation or resuming after a few hours and are now guaranteed to hit the cache.

I've always struggled with responding back to my Google reviews. I'm always excited to post about them on Tuesdays for Testimonial Tuesday. I share them with the team and really appreciate it when we receive a five-star review, but I never make the time to actually go respond to them. I realized that by responding to them, you can also include more SEO terms. Additionally, your ideal customers probably go look at the reviews, and they also look at how you respond, and if you respond at all. So I built a Grok Bot that monitors my Google reviews daily and responds back in a human way, pulling from all of my transcriptions, SOPs, and YouTube videos. It's also trained to include all of the AI SEO keywords to help us rank. Now, every day at 5 PM, the bot checks our Google My Business page for reviews. If it sees a new review, it automatically responds in a comprehensive, appreciative, and SEO way to help us continue growing our Google My Business page. This bot is gonna continue learning from our business, from my YouTube video transcriptions, and from our chat threads, so it can keep finding better ways to respond to all reviews. If you have any type of business or brand, this is the best bot you can use to help you continue growing your business with five-star reviews, and responding back so ideal customers see it. Next thing I'm gonna build on top of this: after there's a five-star review, it's gonna automatically copy it, save the image, and upload it to our website, so our reviews page is automatically updated daily. Full breakdown: xitter.cf/bradsmith/status/21107… Grab the bot below if you'd like 👇 x.ai/bot/zQ6iZJllSSOBD8az-e3…

I'm optimistic for the day when Apple technology has advanced far enough to solve this seemingly intractable problem

The biggest bottleneck at work is waiting on each other. Today Town is announcing its $108M Series B, co-led by Forerunner Ventures and Menlo Ventures, to fix it with multiplayer AI assistants for work. Most AI assistants are built for one person. Work doesn't happen alone. I think the moat is multiplayer. Everyone at a company gets a Townie. Townies ask each other questions, share only what their person would share, and do the work. The more a team works together, the more useful Townies get. What's the thing you're always waiting on a teammate for?