201404211129 23kwz1
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
52356a2210bc0a5aa6e10bdd7d0b0866 4c2837d5e93a29ed59af68c774356ab4 f34af731caf2af5ce3c2782cd7c9672a a6dc7147976f32bef52773bc165ec7cc bb6c3ad6b30bdeab3fd6dc1fb39c771d 34d6f843e3fa80a7fef4013d6f435b4c 81fd9649c53d1c972ec935babc4c1f7c 19af2c1e76cfdd7ce9009e291cb88abb b810466e1eb2e17ed6a779a4413f38ac a12cc8e17bf65453c715b8b8f5c12f2a a7373e2a9d17e95c95f9e34600d8664c 2f957a98f3fcfc24e8b31c8a4251098e 6b2964af6d783fd24d8414b385b6c9b8 c60715199335c786e7571f4bb2b9cec5 b51b3bf9b07434623eac2a3dda69eda9 eaa2d4dcb40272e5b06e55d5e46738c8 fa27c359ede0f1fc6ec2cff254120ab4 bbd5185588763479825bd49fbb9ffde6 0cbe54b8b9d53a06fb057f73ddf56581 e801ecef9347c64ebd1a2550bf4dd89b 595eb45001b0ad9a9ba9259afbf8530d 10ed9383541de3fdc90aa5bf76120a18 5ab040aca7d94d448228bf8ce3ade0cf 07dd5df0d33f2c6c5bdcb3763477ed01 a4d20a7b1513ef3d4db636adfca6fefc 8622672ebee9228eebffa580597a33ea c9f245016d8b476e29f075cecff90a5d ce78fd2b20789892fb2ec23fe1f346b0 0ebc393badb7ed0b554b4989fb96d0f8 3ee391a011190aec8a4c2dc212f99eb6 823a4558389ff7ba3f39340076050104 92384cb732bc083df050db3b4e926a54 5832bff21f108358bf6679161b13063b aee952f3e3ba0aa2a2651a046572e138 6952e9fc405a6d9f
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 124 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.