201508190557 3hj1e0
inferred encrypted filler
N=8
From the post to its content
As posted (encrypted)
80acb5226f4615ea020ee8050c300bd1 fb67ec135bcc09a2be0c166bc8a2e815 10f80d202321dc876aad336e1ec13873 f2da69504132cac173f6a20324bfe66e 1a1cc6fd7cec7aa0ae50d83375966c34 060cf3e83d1c01c9c98febb77c406039 77dd8ee82359ceee81962f48c1b38575 4594ac9969514647c3384841b1c0a5ad d57ee72747db913d4fa4107380529cb1 81f3210981e7c0da8bee55fdfd0f1a77 e4660c89936defeb9cd0c4f48d0ca3c0 b4b09636e1c04c2cbde5828764648b35 51335b69dc3bb018a0c05128647b2e1e 3ba35f85981a4fac28ea82e5751e56f8 302fa3dc0c7d5528f416a870aa2775e9 5348d6027af621b48768cf754e70f57c 47b39e81b2182189
Explanation
- Read the length. 528 hex characters = 64 × 8 + 16, i.e. N = 8 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 7 of Run 67 (seed 466,795,333):
new Random(466795333), Next(0,25) +2 per post. The RNG predicts N = 8; the post has N = 8 ✓. The seed is the machine's uptime in ms when the app started (boot 2015-08-13 10:08–11:01). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.