Engineering Reads — 2026-06-04#

The Big Idea#

The collision between specialized infrastructure and generalized standards often requires pragmatic, albeit ugly, workarounds—whether that means percent-encoding IPv6 zone indices in URLs or wrapping standard S3-compatible APIs to expose proprietary storage features.

Deep Reads#

IPv6 zones in URLs are a mistake · Cadey IPv6 relies on zones (like network interface IDs) to disambiguate identical link-local addresses, such as fe80::. When representing these zoned addresses in URLs, a conflict arises because the % symbol used to denote the zone violates URL grammar and breaks parsers like Go’s net/url. The necessary workaround is to percent-encode the zone identifier itself—turning % into %25—a terrible user experience that ironically complies with RFC 6874. Furthermore, browsers lack support for IPv6 zones entirely because injecting zones breaks the underlying concept of a web “origin”. You should read this if you build networking tools or parsers and want a stark reminder of how edge cases in web standards compound into intractable UX debt.