201406081559 27mdeh
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
12a01fd6f47f1afb7cc0d0c7e5a10203 fff93aff435b039fec38bad5a5d6484d 34f4763f007b75f3be150d9e558f7f55 8a99581452fc907fc4aba8ba093a3691 52424144ecfe1f10122af1efd803cde4 8b629ec395fd923e90b866781315e4aa 4c667a02d83c373d41d0ab4b5a0d1df3 c0640180f4831b29b32311e8fbcc7340 ded35406e593051b6dedbf27d4f23ad3 7ec24e5d1922990ab0bfeff607c076fe ef18d475e88c274f95825c376cc2d6d5 a185c0555a709ea0bc664e0b167a92f2 ce1282d0626db2eb
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 71 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.