THE COLLECTION
Library
Everything you’ve found. Nothing you need to save twice.
19 articlesBrowse at your own pace.
o
Patch the Planet: global response coordination as agents uncover critical vulnerabilities
AI tools found two critical PHP vulnerabilities before attackers could use them. The authors propose a five-stage response framework. Maintainers confirm and fix the flaw, key groups prepare updates in private, and teams publish guidance after. The article also weighs sharing exploit details against leak risk and funds support for maintainers.
openai.comJun 22, 20269 minintermediateRead
s
Book Review: Seeing Like A State
This review covers James Scott's book about state planning. Scott argues that governments simplify complex systems to make them easy to measure, tax, and control. These plans often fail because they ignore local practical knowledge. The reviewer likes the historical examples but questions how far the thesis applies.
slatestarcodex.comPosted onMar 16, 201751 minbeginnerUnread
t
dlab Open Source Week: Frontier AI on Your Own Hardware — Tim Dettmers
Tim Dettmers argues that AI agents make research cheap, so small university labs can compete with big labs. His lab will release an agent harness, a local inference framework, and a compaction method that halves agent costs. He tells students to change how they work, keep their identity, and attack problems that need few resources.
timdettmers.comTim DettmersSep 21, 202618 minintermediateUnread
e
Everyone is doing Git on S3 wrong
The article argues that Git-on-object-storage designs using a write-ahead log, like Cursor's Continuity, gain durability and read scaling but remain effectively single-writer and still need full repositories on disk. The author presents Enroute, which instead uses per-repository Raft consensus, stateless compute nodes, optimistic locking, and a segment/layer format confining deltas to commit ancestry, with S3 for durability. Reported peak exceeds 7,600 pushes per second into one repository; reads benchmark near stock Git, but clients pay more to decode served deltas, and garbage collection remains unsolved.
enroute.shOct 13, 202619 minadvancedUnread
a
OpenCode Reloaded
This article explains how OpenCode 2 achieves instant hot reloading of plugins, config, and MCP servers. Mutating shared state from multiple plugins causes order-dependent bugs, so plugins instead register transformation functions that OpenCode replays in order from an empty state on every rebuild. The tradeoff is that plugins give up direct, arbitrary mutation in exchange for deterministic, coordinated reloading.
anoma.lySep 21, 20267 minintermediateRead
H
Async GRPO with LoRA across HF Jobs: a bucket, a proxy, and no NCCL
A rank-1 LoRA adapter is only a few MB, so async GRPO can span separate HF Jobs: trainer and vLLM replicas swap adapters via a mounted Storage Bucket instead of NCCL, with a proxy adding auth, broadcasting adapter loads, and routing rollouts by KV prefix. Five instrumented runs chase the bottleneck between training and generation; packing, dropping gradient checkpointing, and raising in-flight caps cut 500 steps from 3h27m to 53min at equal reward. Tradeoffs: FUSE sync lag, retry logic, concurrency caps.
Hugging FaceAmine Dirhoussi, Quentin Gallouédec, Kashif Rasul, Sergio PaniegoFeb 24, 202528 minadvancedUnread
G
Testing race conditions with memory access tracing and stack-based delay injection
The author presents MAccConc, tooling that traces kernel memory accesses via ASAN outline instrumentation fed through KCOV, and uses count-augmented stack traces to stably identify accesses across runs, enabling delay injection that forces specific thread interleavings. This supports confirming race-condition candidates, writing reliable regression tests, and eventually fuzzing. Tradeoffs include ASAN missing some stack/global accesses, coverage loss on kernel panics, and constraint-style orderings being less deterministic than fully-specified ones; kernel patches are not yet upstream.
Google Project Zero17 minadvancedUnread
G
Migrating the GitHub Copilot runtime to Rust, using Copilot
GitHub rewrote the Copilot agent runtime from TypeScript/Node.js to 800,000+ lines of Rust, with AI agents writing most of the code across 128 incremental pull requests shipped in place rather than via a big-bang cutover. Reported gains include large reductions in startup time, memory, and CPU, plus an embeddable C-ABI surface for six SDK languages, at the cost of ~$120K in tokens, explicit lifetime management, and some regressions. The author frames it as escaping Node/V8 overhead for embedded runtimes, not a general claim that TypeScript should become Rust.
GitHub EngineeringStephen ToubSep 17, 202665 minadvancedUnread
F
Building Agents that Don't Break Themselves
The article argues that an AI agent's long-lived process (its 'home') and the sandbox where it executes model-generated commands should be separate environments. It presents two Fly.io case studies: SpriteDoc uses a throwaway sandbox per session with per-command credential injection, while Hermes Agent keeps a persistent per-task sandbox. Tradeoffs include lifecycle choice, idle cost (sandboxes go cold), and replacing approval prompts with sandbox isolation plus cheap checkpoint/restore rollback.
Fly.ioJun 8, 20267 minintermediateUnread
F
Your Agent Speaks MCP. Give It a Computer.
Fly.io pitches Sprites—instantly created, near-free-when-idle cloud computers with durable filesystems—as a better agent runtime than stateless sandboxes. The substantive argument: the MCP-vs-CLI debate conflates layers; progressive disclosure is about what enters the context window, while MCP handles transport, auth, and structured results, so plugins can layer skills over a hosted MCP server. It is vendor marketing, but the layering distinction, safety annotations, and guardrail defaults (org scoping, five-Sprite cap) are the meat.
Fly.ioSep 3, 20265 minintermediateUnread
C
How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
Cloudflare details five Rust memory-layout changes to its 1.1.1.1 DNS cache — dropping Vec/String capacity fields, merging record lists with u16 offsets, omitting owner names when they match the query key, boxing large enum variants, and storing record data as wire-format bytes — cutting per-entry memory 56% and freeing roughly 100 TB fleet-wide. Performance also improved (inserts +43%, lookups −19%), though each change carries tradeoffs: allocator overhead and poor locality from boxing, sequential-only access for wire-format buffers, and records no longer self-contained.
CloudflareAug 27, 202612 minadvancedUnread
U
Uber’s Real-Time Push Platform
Uber replaced mobile app polling—which reached 80% of gateway traffic—with RAMEN, a server-push platform built on Server-Sent Events plus a custom sequence-number/acknowledgment protocol for at-least-once delivery. Scaling forced a rewrite from Node.js with Ringpop gossip sharding to Netty with ZooKeeper/Helix, reaching 1.5M concurrent connections and 250K messages/sec. A newer gRPC bidirectional streaming version addresses delayed acks, unidirectional transport, and text-only payload limits.
Uber Engineering17 minadvancedUnread
D
Infrastructure Update: Pushing the edges of our global performance
Dropbox explains how it reduced transfer latency for distant users by deploying Points of Presence and edge proxy servers in multiple regions, absorbing the TCP slow-start and TLS handshake delays that undersea-cable round trips impose. Proxies hold persistent connections to data centers over private backbone links, with TLS 1.2, PFS, and certificate pinning preserving security. Reported gains vary by market (40% to 3x median speedups), and implementation details remain high-level.
Dropbox TechAkhil Gupta4 minintermediateUnread
T
How Tailscale Peer Relays saved my holiday: a 12.5X performance boost from India
An engineer traveling from the US to India found direct Tailscale connections failed due to symmetric CGNAT on Indian ISPs, forcing traffic through shared DERP relays throttled to ~2.2 Mbits/sec. Self-hosted Tailscale Peer Relays (a node with an open UDP port) restored 27-35 Mbits/sec and cut latency ~150ms by removing the Chicago relay hop. The article explains NAT diagnosis tools and relay setup; DERP remains the fallback, and the tradeoff is operating and exposing a relay on your own infrastructure.
TailscaleRaj Singh7 minintermediateUnread
U
Service-Oriented Architecture: Scaling the Uber Engineering Codebase As We Grow
Uber recounts migrating from a monolithic codebase to a microservices SOA (500+ services) to handle rapid growth, which solved coupling and deployment problems but introduced issues of obviousness, safety, and resilience. They adopted Apache Thrift for strict cross-language service contracts and built client-publishing tooling, drawing on Netflix Hystrix and Twitter Finagle for fault tolerance. Tradeoffs include immature Thrift tooling for Python and Node, and no header support complicating authentication and tracing.
Uber Engineering5 minintermediateUnread
D
Improving infrastructure efficiency for growing demand in the age of AI
Dropbox argues that as AI-driven demand grows, getting more from existing infrastructure matters as much as building new data centers. The post describes a system-level approach spanning power management (Deep Sleep), workload rebalancing, higher storage density via SMR drives, and failure-rate-driven hardware lifecycle decisions, reporting watts per petabyte improved over 50% since 2020. Tradeoffs include density versus power/cooling needs, energy savings versus latency, and longer hardware life versus reliability risk.
Dropbox TechIlya Yakovlev10 minadvancedUnread
D
Testing cookie behavior across hundreds of web surfaces with our in-house auditor
Dropbox describes an in-house cookie auditor built with Playwright that simulates privacy-conscious visitors (US, EU, and Global Privacy Control signals) across 200+ web surfaces, verifying consent choices persist and only appropriate cookies load. The article argues browser automation was the easy part; most effort went into translating legal concepts into testable rules, maintaining a current URL inventory via traffic-data analysis, and separating real violations from false positives. Classifications live outside the code so privacy staff can update rules without engineering releases.
Dropbox TechYasmin McDowell10 minintermediateUnread
C
Have it both ways: stay discoverable in search while disallowing AI training
Cloudflare argues that mixed-use crawlers (Applebot, Bingbot, Googlebot) forced site owners to choose between search discoverability and refusing AI training. Its new Disallow AI Training setting publishes a robots.txt preference that 'Accountable' operators honor, keeping search while blocking training; Block now applies to mixed-use crawlers too, affecting search. Settings migrate automatically on September 15, with stricter presets for ad-funded sites. Cloudflare frames AI summaries, with only partial controls today, as the next unresolved tradeoff.
CloudflareSep 15, 202611 minintermediateUnread
C
Saving another 100TB of RAM with math (and Rust)
Cloudflare cut ~100TB of RAM from its Pingora Backend Router by attacking pingora-ketama's consistent-hashing rings on two fronts: packing the per-point struct from 8 bytes to 6 (25% savings, done via a raw byte array because Rust's alignment rules negate simply shrinking the index field), and reducing hashes per server by 90%, justified by a derived formula (CV_k = sqrt((N-1)/(Nk+1))) showing the last 90,000 of ~100,000 hashes bought only ~0.7% error reduction while 32-bit collisions actually made error worse at high hash counts. The tradeoffs are that fewer hashes raises the theoretical load-imbalance error margin, and changing the ring re-routes cacheable requests and would invalidate cached content, so both rings ran side by side per request and the rollout proceeded data-center by data-center to limit cache churn and blast radius.
CloudflareSep 18, 202614 minintermediateUnread