201406042000 27bbun
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
63caeb3d61db1e58ae2fa1a473d38146 26cafa4a310a7ae7ff77edbac78289be f8d39ab8d5bfe488be1d7891254f4fe0 62f4e3949d3bcc3d0e960a28a4ccbbbe 3e0c5429caacb307041965befa5637e2 01d09964603bd2a104f3dce3b139c484 f6e680c352fcd0bdb5a38ae5290eb89e 9144644a95507c81ddaf18dbc8c11b17 b18867ca8f0719b6407c6705733f9c07 df28fc91ed4288837793f3c440ced3f6 82a65e7bb347209a3105d8b565e3edd0 b19ba76158acbd38ac8797213e3e5e72 2c86ae27c46c4701
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 25 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.