201511190659 3tf9nk
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
96c09e01109b0253eef60c2dbd82a31b 8a387feea7879694b7169266a292c0cd bd2641914dd7df79fc0fd17021e5e246 19509b16f47427336a6c9adf56d56e26 8b102bf91f47ebfbfc0788c044bc655a 61493ad90f6d2e469caae78b51291adc 9946405e1b29bce5606d0008f4227c4b 4a987d171e075ccf7f92450337598ee5 a911b5c3424f30887ac5dae14d02c8cc c3d9f8ce7deea7d8edf8437c16c808ac 4f892772ddf512178eda80bfb590b5ab 6bb8a6866c2fc24e289c37176f75bd64 441289fdd6c01672ac39fe9a7df1d1d6 30da803cf0bd7f865b2c1ec9de42ad4a a58f3fc9484033624186e99451b955c6 56044c7fcf9ca7c074553937a450d42f 22b61b11361715b683860ff0ea6fde4e 9b475f03ec30ea64b965dec64a9b5a7e ffb74a39ad039fbd7e5b39adeb5fa0a3 084d9797aaec163c4a66fc65cc240650 4545781289b2e823576b58e73ed2fbb8 6a90f4c8cd19c62dcfb98a3eb4e5f839 ef4688b31fd0e99e9075565780903232 1f9d2989a92da0d61c62d7cd0f934d81 82aef49f453ace3e9def6e334854eff0 d11e8fff12adc3f24c2fe5faa5a1e3d2 6ad182ec25990c785a1e76b94a24f614 ddf6a35a51d1fadf22cb3e1aa961b8ea 18777cf090ed7f60b5310a571f008b76 4c076afbfd2b3ebe8daddafdf8db8396 c72e2b72a4eea13de2719b1de8f5dc41 c4fbecc45542bccfd627e8d8bf561bcd 7d43e1720cfdf61e3da6d160bb1ec19c 732678152b69c8dea919e3ebebd1df25 d2cd6a79ff5349ca
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 89 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.