201404082226 22kt3z
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
a47b083ddfd3f6152bab13a3a84ea757 6e5df7f1fa94d08c91f5c13f2a703ab2 2d98657e98048584506c58f218d1e4fc 81612cd64f56a06f181e73aab33eac56 597bda3c96d3a83b9663c176538877b9 44d9508cc75540ce9a45b6972440b2cb cf74727657c72774ba7174f56f8bc7fd ce136543a381c204c5e5baf87f155e62 36928d55486cac96c882ec5cd51b1c4d 78c58fc5f8f0180c1ea044b222e73497 e3be039f36e9b330400df7a8420c2451 851584127ad3ca5d7ce9b93175232093 56f9ab0e2c3f900c
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 29 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.