Hacker News new | ask | show | jobs
by jakeogh 659 days ago
That is the real issue, because ultimately, this is about the memory hole. A re-upload of a camcorder copy of a VHS is no threat; it will be degraded (again) when the digital archivist who saved it's re-encoded copy[1] (from whatever video platform deleted it) posts it again. Intercepting a exact bitstream circumvents this modern camcorder copy deliberate problem, and would ultimately obliterate the non-arguments to keep the original file unavailable.

On the other hand, a signed sha3-256 digest along with the original[0] file before YT re-encoded it (and stripped it's metadata) is unobtanium for the plebs. It is the _most_ important data for the host. It's the first thing they backup. As far as I know, they (YT/Rumble/Tora3) never talk about it. Some would love to only serve hallucinated (when convenient) upscaled derivatives.

Power is threatened by persistent lossless public memory.

[0]: https://news.ycombinator.com/item?id=20427179

[1]: (Mr. Bean, 2024) https://www.youtube.com/watch?v=xUezfuy8Qpc