Follow AI Builders — Not Influencers

Yes each of my sites is a Termius server with this kind of start command cd /srv/http/hotelist.com && tm tm is a script made by Claude Code which puts it in a tmux session tied to the project name (from its folder) That means I always log back into my tmux session for each project! My big sites like Photo AI are on their own VPS, one site per VPS, but the rest is on one VPS, all on Hetzner btw, so anyway I don't even notice this, it's just all tabs in Termius If my phone disconnect I just reconnect and am back where I was Every tmux session has Claude Code open

3,000 visits per day now on https://outlike.lol and the board will reset every Monday so you can reach the top quickly, for free go steal that traffic new top now 👇

RT LlamaIndex 🦙 Our 2nd founder dinner in SF co-hosted by @jerryjliu0 and @GuangyuRobert at @Fundamental - the team behind @tryshortcutai Talking about existing moats in the AI era. Frontier labs are moving past model APIs into vertical agents - ChatGPT Health, Claude for Legal. So where does the moat sit now? ✅ Agent engineering ✅ Infra optimization ✅ Domain evals and data ✅ Workflow expertise ✅ GTM and brand If you're a founder or CTO shipping agents in production and want to know what other teams are doing to maintain their moat. Request a seat 👉️ https://luma.com/llamai-8hry

RT eigenron we're working on sim infra for physical ai at @AntimLabs and want to meet more people thinking deeply about sims especially interested in sim2real, contact/dynamics modeling, system ID, DR, r2s2r, scalable scene generation, synthetic data, and sim evals etc. researchers / PhDs please reach out. would love to compare notes.

i highly recommend using the in-app browser on codex.

I haven't directly connected my bug board http://ideasandbugs.com to my AI because I am very aware of prompt injection risks One safe way people mention would be to only give the AI access to collect user bug reports and feature requests, then do pull requests on GitHub that I then review myself before I approve or reject them But you can imagine a benign attacker can prompt a feature request with an elaborate prompt that tells it to add a backdoor to my sites BUT then in that prompt write also to report this bug in the pull request as a complete different bug like "pagination fix" and then make the code changes cryptical So now you don't see they added a backdoor to your server and you think you fixed pagination Until that time I'll just keep manually reading bug reports and feature requests and copying them in Claude Code on the server

If your terminal ever gets into a 'bad state', like garbled outputs, you run 𝚛𝚎𝚜𝚎𝚝. I noticed it was… oddly slow. Turns out in 1979 3BSD's 𝚝𝚜𝚎𝚝 had a 𝚜𝚕𝚎𝚎𝚙(𝟷) to let mechanical printer-and-ink terminals 'settle down' 😂 I asked 𝚏𝚡 to write me a faster alternative in Zig. It takes 1ms instead of 1s. It was really cool to dive deeper into 𝚗𝚌𝚞𝚛𝚜𝚎𝚜, 𝚝𝚜𝚎𝚝, 𝚝𝚎𝚛𝚖𝚒𝚗𝚏𝚘, and the myriad ways in which your terminal can get… cursed. It's legit fascinating how far back our technology stack goes, and how enduring good system design is, even with the occasional 'spider webs' you can find. Check out http://github.com/rauchg/rst for a fun explainer (and some alternative solutions.) ps: once you start using 𝚏𝚡, you'll notice slowness like this everywhere :D

RT True Ventures Coming to Connected Stack in SF — @jerryjliu0, CEO & Co-founder of @llama_index, nominated by @GreylockVC. LlamaIndex is building document infrastructure for AI agents, with LlamaParse purpose-built for the complex documents that general-purpose models struggle with. See Jerry Liu on September 10 in San Francisco. Request an invite at http://connectedstack.ai.