201404200629 23hr12
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
79832153d83dce60d21e183e4ecae95d 0828b939f749ffd0456531079aaceba3 af9e08415c1c1a0b56b45a4cd6be207f 9b903a0b90f6d5bd894fe13e81f70d50 2281fa25b1eeecd8fde4ab4bee93f2e7 46ffc63ef033511c0e50825a40637319 a6676855ccee64feafeb39873ba8610c ec25338e1e32e533e248a3b6e3d99f4f ca7b5ed819bfc71bb495d33ecc99b001 a940bc76630ef1cba1a1646cc89d90e1 607f67a3cc9ed7b2fdea554c22947d3a 5540479405bf2cabc96a373b6c0d3710 c53e7ad48ac66213643fcd0493af15ac 0d5868e28e93d4f1cfcf2af2aff7bb2a 8e3248acac684ecf65984f4b5de4e1db 7f014d0cac1a85213e67a410ca4054f7 54638799e83ded64b10e1433b92da732 decbf1ed7996bc325881f3971a2d08b4 7c589d525fd3151b462f5e7a69e23bec 5e9f3efe2b59a87e8c24b4677f61f6f1 620b8e046926837a20dc8b5ff1eb043c dfc67066814a3a3736e8c00b5f9df5b9 b77da4a444456753da2887877dc66af9 1472f2c4144908c6591048a9259ca34c e3fa27527af113e18afc5061277e29f8 b6bcab2d381a9c0e364aef179710612d 60af9c30e8a72754f207ceecce16cc0d e15d3174e44d47d37a33b2e65ad0c524 6f0322f16da2fb2b1a952793b52b335d 061cbf6c813f705fbc721568119d7d48 8f6ee7a942e67be8d673164f7451d31c d36270c0223c9c3e00367f554c73c20d 08424e5d7ecf528afec28a216f1358c1 f38a89e0942ee0c4695ff583c17c5755 fcb231894bbcaca6
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 95 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) 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-04-10 09:27–10:27). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.