201403130000 20aknf
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
ac5c2b07cda8081c6cb964c3ca5ef1fb ddd639c1c78a5aa24361022492d08437 7b1cfa1969aebd7b16bd50e2fa1391a2 8474f15c0f3c08733e6e0878d96e8729 32f1ff4c591adc332bdd575faefe42f9 784e5a93a4879b17f5ab62abc1ecc7da c1e41fa145c7ec4a08966f4659e394b2 b203624d4b51aade0349fa09cd7bbab9 12aafe22b301490f721ab403a0bde332 d5ee38f1dc864526d4f12df25123bd42 0a2aa90d19e224ee0294b01790ac2e08 b3898e7226437526ab781ee9f3663128 56dcae80b21c1455
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 7 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.