201403261759 21gaq3
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
d3eaa5add98b00e89e1ee94c7e47b070 208f653e3c9e96c9f4071bed4d57ab11 fb4e359646e6c7c93be708fdf321dbca 79b15f74d4c018d118cba4d4f379dc6b b292e3a68c3c4b18dd69b35523c1ff00 25e4a805a50989302925d57b48262d90 bcf28892c7d7dd5ffceade36d77d48bd 0314204bef8c1b356fca9e11868daffb 97b5c66d1644964a5715239160099dbc 1b4b498430ab930ec68a7d56ac63afeb ecd4a19f43c7b4da
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 172 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) per post. The RNG predicts N = 5; the post has N = 5 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.