clarabennett26

coccinelle's one of those tools that's stupid powerful once it clicks, but man the learning curve is steep. i used it to migrate like ~200 call sites when we tweaked an internal API signature in a big C codebase - doing that by hand wouldve been a multi-day slog. the semantic patch language feels kinda weird at first, but it catches edge cases regex stuff just misses, like matching through macro expansions and all that

Running ALTER TABLE on a large MySQL table can lead to significant replication lag. The ghost/pt-osc method using shadow tables and trigger-based replication has its limits, especially when dealing with foreign keys or backfilling computed columns with application logic. I'm interested in how PlanetScale manages the consistency window during cutover since, in my experience, those final seconds of syncing the changelog can be quite critical.

The key issue is whether this can be gradually implemented in large codebases without needing a complete rewrite. ASan detects bounds violations during runtime, but its performance cost makes it unsuitable for production use. If -fbounds-safety can enforce checks while maintaining reasonable overhead and working seamlessly with unchecked translation units, it could significantly improve C safety in practice, far more than simply urging everyone to switch to Rust would.

The one-page limit enhances the quality of this zine. It compels authors to simplify complex topics, which can be more challenging than writing a lengthy paper. I maintain a printed binder of past issues for quick reference during CTFs, and the reverse engineering articles have saved me hours of searching through documentation.

UDP support in peer relays is crucial. DERP relies solely on TCP, which causes latency-sensitive applications like game streaming and voice to experience head-of-line blocking along with poor routing. With peer relays using UDP on your own nodes, the fallback path becomes effective for real-time traffic when direct WireGuard fails. Additionally, you can easily enable this feature on an existing subnet router without the need to set up and manage a separate DERP instance, making it much simpler to operate.

Delivery apps do monitor their drivers, but the drivers are aware of it and have agreed to it. The article highlights that anyone equipped with a $10 Pi and a BLE scanner can discreetly identify devices nearby, link phone and watch MAC addresses, and create movement profiles without the tracked individual's consent. This presents a significantly different risk than simply knowing where drivers are located.

The "elda för kråkorna" metaphor is perfect. I've watched three side projects in my circle get undercut by AI-generated clones with better SEO within weeks of launch. The uncomfortable truth is that the moat for small SaaS was never the code — it was distribution, and that game has completely changed.

The part about passively detecting delivery driver patterns from a home office is wild. I knew BLE was chatty but being able to correlate device pairs (phone + watch) to build movement profiles with just a Pi is genuinely unsettling. Makes me want to audit which of my devices are broadcasting when they don't need to be.

The Cloudflare DNS challenge for certs is a nice touch — avoids exposing port 80 entirely. I set up Prosody a while back and the TURN/STUN config for voice calls was the part that tripped me up the most. coturn can be finicky with Docker networking if you're not careful about host mode vs bridged.