We've decided to sunset Arc on December 22, 2026. That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community. Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward. We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how: · Your passwords, bookmarks, extensions and history come over to Dia seamlessly. · Spaces, Folders, and Tab Groups are in Dia and import over with your data intact. · Dia now surpasses Arc benchmarks in stability, speed, and security. · The browser features you use in Arc are free in Dia, and the AI is optional. Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.

pro tip: run a few agents whose only job is to keep deleting tech debt and doing cleanups. Agents write code quickly, which means they also produce clutter quickly. Dead code, near-duplicate helper functions, unused imports, stale feature flags, and comments that no longer match the code pile up much faster. Cleanup is also work that people rarely prioritize (being super generous here). A few things make this work (call them cleanup agents) in practice: - Keep each cleanup agent narrow. One removes dead code, one merges duplicates, and one updates stale docs and comments. A single "make the codebase better" agent will actually rewrite things it should leave alone ... so, bad idea. - Keep the changes small. One focused pull request per cleanup is easy to review and easy to revert. - Let the test suite be the judge. A cleanup is only valid if the behavior is unchanged, so every change must pass the same checks as any other change. The last point matters most. Agents can get this wrong just like people do, so tests and the review step should be the gate. Deleting code is risky, but having your agents call dead code because they think it is still live is riskier. Hope this helps.

You just woke up and all your projects are on Railway

If you use @tailscale and work off multiple computers add this to your AGENTS.md file: "Any time you give me a link to something running on this computer (a preview, a review page, a dashboard), give me a Tailscale link, never localhost. I work across several computers and my phone. Publish it with tailscale serve, open the link yourself to check it works, then send it."

php2shell Security Advisory: two critical RCE flaws in the PHP engine affect PHP 5.4+. Public exploits are out. Vercel WAF rules were shipped before disclosure and have been blocking known exploit patterns. Patch PHP to 8.2.35, 8.3.36, 8.4.27, or 8.5.12. vercel.com/kb/bulletin/php2s…

I'm honestly surprised to hear that PHP is still powering 70% of all websites! That's really strange to me. Why is PHP still so popular?

An urgent notice from the Railway team blog.railway.com/p/security-…

Officially we linuxified MacOS. It flys now!!!!

agent apps built on Electron were a mistake @theo @t3dotcodes

Tauri it is.

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…

it's here (finally) 🌑

Introducing Pixel - a library for building GUIs in the terminal - 120 FPS pixel-perfect graphics - Embeddable inside existing TUIs - Built in chromium webview component pixelgui.com