Ryan Townsend follows up from his own wroclove.rb 2026 talk: HTTP shared dictionary compression is done at the HTTP layer, so it also applies to APIs — REST, GraphQL, and presumably MCP once clients support it. By putting all JSON keys and enum values (with no PII) into a shared dictionary, requests and responses can be compressed close to Protobuf-size on the wire while still using a flexible JSON API and without a rigid protofile contract — useful when you don't know ahead of time what your API will look like or want to evolve it quickly. Emiliano agrees that this works around the exact protofile rigidity that makes gRPC hard.