Proposal targets net.IP.IsPrivate misuse as an SSRF guard

A proposal from JLLeitschuh argues that net.IP.IsPrivate (and its netip.Addr counterpart) keeps getting pressed into service as an SSRF check across the ecosystem, and wants the semantics extended and the docs sharpened so people stop reaching for the wrong tool. Given how often this pattern shows up in real codebases, the discussion is the one to follow. On the writing side, a three-month deep dive into building a PDF engine from scratch walks through what pprof, the allocator, and four optimisation passes actually teach you about Go. It is the kind of post that justifies its length. Elsewhere, a thread asks whether Go's HTTP/1.1 handling is exposed to the current wave of request-smuggling concerns, and a piece on graceful shutdown compares four approaches from naive to full traffic draining.