201406101959 27t5qg
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
43f8b9deb00b737e36c44ada19e70f63 100d9c1397296c64f30eb1c605fc167e 2f7a08683b395a5075623a9cea1c8d94 2079f4f8f7a2b5817c56f4f8c67984b5 b02ccf7910d8d0a2b284b7009ef07a40 93fb43c166979e1a27a5865d13decd31 bbe693bb75d79f3b456db44cdb93e7ac 313c7ef96bbbf77f34a8b81c13b81e1c f45fa422195094a142884ca06f3d3e82 48c8435aa86b3b71e7afcf930ee91a1f 061fb0f8f5252d4b0823c6642f0ffe91 6e9ffef8067312c5d2a24a330f639ac8 d917418b67a29dde
Explanation
- Read the length. 400 hex characters = 64 × 6 + 16, i.e. N = 6 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 97 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) per post. The RNG predicts N = 6; the post has N = 6 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.