201311170459 1qtpn7
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
f3dd54eced391043f8a1ed0cc1362c9a b42b87c60f050faddf7da39d492914a1 f02a8fffeef65f26b0a48d4350f2f5f6 055be86938e2f330a1a28ee80184d89f f0a87389fc3f60d117ea6e1cca686ee7 4039751a373942f26bc3cbd86aa65647 f8e2838a2b02176a817ed0dfaa68dc8a 5fc9f005bf45f6a23f62e5f55e115589 a9df6e248de6f6ab14076a61d69f1c59 bc970293b1c4c4e3b6fe3144d0628c64 46aa5775c73c46d1da659d1f4abb15ed 4bf1ed38f737d817a93f8c5b28b18de3 e465f29a2f58622e
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 39 of Run 55 (seed 135,104,921):
new Random(135104921), Next(0,184), then Next(0,124) from draw 193 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 2013-11-14 10:28–11:28). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.