201511261500 3ududq
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
b8809aa821041b757b636d01b6f0efeb a946f2c066c6f48fbbf9572a67049a73 1d6b0d47e43adc71fb3aeb9a83851e31 ca0f27623bcd6fbf15c83ad7829c3498 c674de09fa6b16f27781a80ef8be4203 6f8d1c6356b5606dc2a184ac8c901fd3 53e941c30a9528541f42b5ed86c47fd1 3d026b94b74c913bad5c9f7bd7e267f3 d70b19757977b8834b8902d5fe55fe2d 1927a173706c58e869664b24aefe5d60 23052969e5091fbc0eefef43c1ecb026 90371a9d6e3bcc04cdb9466ce516f7e3 a3bc4309c62983785b8727dd1a79fb47 819f3967bf94c7aaf8cbdd77c36e4ccf e9e36ba7d499f29535a8284d823bebbf 8e3a44daf94811f927473b7876d4a4a0 494781ca79c01a2df12341a10469e9fd 78ae91448faa66220514589020e26c16 a7b5d9d9e0a7f8496e7180a9965cd7eb 72a03bbf818579c3eac7d10537a3f71c 66008bd4377b9eb2a6f576bd5682fa75 ac052c6000395fcb6e78bbca181c555b c486700ef3b65dc1ebe4c1039485e77a c4db51cacf878d3177e389a618fd20c0 a29a1b806c78c77c831fd8842adf8d09 cb47baa18ca791f23c9a847022e94549 8d890f230780b2989f7821f339b5e7fa e61461b64fcd4ebce3d02efa8fd54c46 f9acf8f97c0fb4c6d957dd969334e2ae 1640d7bbd99f4e9cab56c1c8d787737c 94b557593a4bd8cf23faa3791664c0eb 077a0ec626b62f4a718f513209e6f752 432b80d28f894b6a3376dd2656a587eb 57b7291ee0b35cecf26c8a47dabaaf86 eade62a24ec7a1b0
Explanation
- Read the length. 1,104 hex characters = 64 × 17 + 16, i.e. N = 17 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 511 of Run 70 (seed 6,038,486):
new Random(6038486), Next(10,40) per post. The RNG predicts N = 17; the post has N = 17 ✓. The seed is the machine's uptime in ms when the app started (boot 2015-11-17 21:21–21:46). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.