201312201532 1tck7e
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
f0146dc5edc8db3099a241ecdd91bd5b 64c122b187c2ca1ac00ae774e1e08dd9 bcd5f64f3e57df1d3038d96018578f08 3d42d3dc6755a32b3b6b971d31bc43f3 bc7774e213973fa06d28f0d309c1ff15 34288d76b30c122e2bcf33cac45311e2 d7712e63bf34f1c7cce32d62a08b5c27 49fc4da4ec739c62b834d0d2c6e400a2 e3fc9a4e6c4b2107f5147529b0e687ab 6655c117612e1ba71badd720c3d9aee6 6eff24b4214f3c3c948794181d710e1f 047e7109305ff3728fef49d88c28858f 49a53365c67de243
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 20 of Run 56 (seed 561,089,375):
new Random(561089375), Next(0,98) 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-12-11 20:41–23:41). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.