201402080514 1xbu4s
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
c6c03709cf651fee90c9067fbc722551 9a5d2dc085dcc844e7c379c2b731a788 df136fd0d8fdce52275a144e313df782 c48072256b741bb5091dd30aa3fe22f1 eceb5b9e17c815064aac4339c14bbbb9 8f2f23fb0849c87dfce946c208780c6c b8ffad6c25e24c233e49fef65748b48e 5052ca87fe2236b2b6689a1802535fa0 954b7b769fc86b835bee71b02b38c4cc e7bcc15af1f99051cc349d9ad2b51c21 552971095e995d23
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 2 of Run 57 (seed 758,305,750):
new Random(758305750), Next(0,44) 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-01-30 00:36–04:36). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.