201512100501 3w7ed2
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
751c47003b5b8e72a157f92d4542c9be 1b377f36c678d7a775f2c590f23cecb3 340a9f9a44cf43a6ee654736a51ce11f 2be33723b482bf188d9eb3aaf9790e7f 600cec04f071df5b84a259c542f1e5ba 42d4a4f23596ba545eaa274855939800 9c4f9d937ccf09c4364c770fd6e66a02 bd8862ea0fbbd51558e0e7b0529279db af70ab087a1df218877835f6ea023d89 fd3ebaf877c097593fe30a74537dd4f2 dfae42b084a7ad529c688841decb9a8d 95789704ca3220b951f461b1c31b5009 28c9ed1b6dbe0ed972cd7f00639eb70c 9ea24d37c3477fa4eeb1c10db9d3e41d a010a09da919b98ee4832dbc86193116 306c94292d1096c2101db11e51ab0ff7 62379d3a0e867c8b5097465d4a77085c 5757293c312d0a4363e8556eac554610 e01ecf61e8d9bc07ed04633b53d03860 d5ca47e5c3d937e674d43f8136fa7209 5c606ad4cdd57a6c6649cfa9b01bf92c db69f6cadecb83edff29a4faa5c5d175 6f5819cf5b6dab1c44d9c83aeb9c0562 29c84b9288a85dc315546689a02a3b5e 509a267f060e88d3437a4750cd9692cc b4d2678d895ff395f22dd66216909e25 d6dff5ff4438cfb44e50d9e6d54e877b d710a3c17c231c855444849e2533088e d6ecd4ce5c84a2d025646a1e6b475c9e 22a15d4e8ef4db25b4bec4b7ed55faf8 0c34e3bff7efe243fff832f628f38500 1812f3d840e0d03d54cb6b3fc024f25d d2a36f372ee88bfc298aba0a9ef25822 50a1dd3c7f09f500f03179f56228f7c2 477d019269f153e1
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 202 of Run 71 (seed 1,220,915,585):
new Random(1220915585), Next(10,24) 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 2015-11-17 20:51–21:51). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.