201406091159 27orzz
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
0a1e25e5e95bfde63be94cafcaa5e894 ec159ce76403161896ea8b6c0d254adf 3e38698814927978d3a455c3498964dc c7910df3cabf68e5429fccb8db323016 83813fede72cd520efa7036f54bf64cc 15efaeb3962d811ada9dd19569628b4e 50374e28b181f5d430a0f5fbc34b114f c232937cf0d0737e3285c67f29fd69e1 298afa2f3259727d120b9a71603e5b2f 416a749590b320189cc9279ae11f92b7 cc8679a0c5316bedb44e4588dffabbed 6254dd49ed68755d26dd500007f6fcd3 ae17f9bf6dcc6ab35592bde9daa67857 aeff3df1b84ff00598a5ea42dee0e232 fc3facdcfc755039
Explanation
- Read the length. 464 hex characters = 64 × 7 + 16, i.e. N = 7 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 81 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) per post. The RNG predicts N = 7; the post has N = 7 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.