201403102259 20317j
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
62157664bf6ccc5311da081a7c549e9b f860ba3b53f3e4d7716c799c355d7445 3868362c4d276717ab1ae73be3e81764 7c5d913836823b6da66a553305aa78fd 101f4ea13316a371496e0eff2ae04ba0 f37b5a1106089e10528a8282500fb639 01c924f89a9273b4e3373400232b514a 2171b9b71da895ea88d0640b37b93004 b0bfa070a812fab46c1a13b87149b5c3 47fe38851a1151fc62132896744fc113 153363793941f48276393d70d878399b 4a2e9eee263bb9ff0e3286e0f4880940 904865c786a267477fddd1a9c7992e3c c53d15f2cea1ae3410c156af6e59d2c7 5978803f4d7d4a2244efab68de982731 b480379054ef11c123f5edecd050d7d0 985ca109f59625fcd884105524663b5e 2a2dfd2bd3a20154669d156c16b08fa6 33900161a9e1e1d241932481250909d0 274335e339611cbd958581eddd940602 788e64355c92a9eabb6d7f9a5b34b2ce adc841201145005d3d69d77473231f14 5ea3c3a3ce01146c5a39d3dcacfbb90b c78bf518c4e2b0b1978fc87213092c80 36e2f8c6cc41b57a8aa724542cad376d 749c05140becd06cad640e2660f9424a 4d1fa2ee20b94d0d5ce9398f46c4f17d 16076402f55156766e06a69a7d8fb892 8fa39aec87f6c17b28730ae9de618626 fb155bef6dc30f0518f006395e8dbf9a 291bd68a637d5179e6ce6bddfd7cee07 9bfa56ca567e2021133564ace7e07a2c 7db1c3544b1c8042b4e8c82437baf97f a5b458703c1dd2f52bafca757f49da2d 725d98d1f0f0b46d
Explanation
- Read the length. 1,104 hex characters = 64 × 17 + 16, i.e. N = 17 GUIDs encrypted with 3DES plus one 8-byte padding block. Every post-cutover filler post has exactly this shape.
- Key unknown. The post-cutover key (2013-10-16 onwards) has not been found, so the GUIDs themselves cannot be read. Everything else about the post is accounted for.
- Explain the count. This post is draw 35 of Run 59 (seed 1,704,050,750):
new Random(1704050750), Next(0,36) per post. The RNG predicts N = 17; the post has N = 17 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-02-13 08:39–12:39). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.