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.

Giving your Go apps Tigris superpowers While S3-compatibility is a practical baseline for modern object storage, relying exclusively on the generic AWS SDK obscures provider-specific features like bucket forking or object renaming. To bridge this gap, Tigris authored a custom Go SDK that offers a drop-in replacement for standard S3 clients while natively exposing these specialized operations. They also introduced a higher-level simplestorage package that infers configuration from the environment, optimizing for the common single-bucket access pattern. This approach allows teams to adopt advanced storage capabilities incrementally without rewriting their existing S3-compliant codebases. You should read this if you are designing SDKs for commoditized protocols and need a clean pattern for exposing proprietary extensions without breaking upstream compatibility.

Connecting Thread#

Both pieces grapple with the friction of building on top of established technical standards. Whether struggling to fit IPv6 zone metadata into the rigid grammar of a standard URL or extending the ubiquity of the S3 API to support modern storage primitives, engineers are consistently forced to write abstraction layers that smooth over the rough edges of foundational protocols.