201404082014 22kgx9
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
342e2b3a67639982254fc3e9e27657d9 b6a0aa915465b6ac889ebb7706ed269e 5ae5f64074e6624b57481906c30b77f6 1de46f16ffc914a98135b8d155fbf91b 2e9c31ca531b09e7ff103bbc1c8a3c2f e3d262fe0dd59403afe8bba9f870dfb2 58b567066960b089d11e7ed007e8f88d 0c9d801ea531db52e59bf16c52cc81b3 1a3466298b15bd3572e829ba1016d936 31b50906f433979dc435d24390c1f070 8390cdc5a6477cf0d5e63cd8c4695933 baf6423404ee192a7db84b9e89289484 cfd91f803c5f94fe
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 27 of Run 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) 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 F 2014-03-12 08:00–09:06). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.