201508280801 3ipti5
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
2c9b36954d4ace969f3800a87669af98 395451df8246fccea7efc5b2a818328c 519b61d376a9c1bb0f3b8c2fa2f43ebb 945132a90304d19e96b41a65fd5856d6 809916afd2121f96528cc94eb5712063 2d8587b965feb8e025957f1afb1c149d 1a1af94a7cb6b4e06443131981d62d54 19be48e9cba1ac100ac682c7e1c7907f e0d4bc09abef7f4ef378727c9aba499d 785fd17a2c864f3e1ab06789e5b1edf7 7d84a55a1c5b81c25cdc7f4808ef3c4e 627a6a24d76f425357a5f234ceb3a73a ee22fde5c9c021e3a7482ded93331aff 16a5efe0a10bf1bd12b2e9d8bb64a97f 3e60823c626e6046e584fc783eba248b 80bfbab0f7eeb1ccc85e4039f2c31c2e 7fbaf76ef83d07613250a8c759f6f20c 0cb0bacbd340fb2b7579d9315d2bf9be e8bc5aa1d9c4753504f8d31c0aa64112 796f5aa8f8cdc584976665a48076a78e f32ff99c69e08a842e635f8af93d80cc 9c537798886a29907f73140957e36ec7 a391333acd9a83e8bfab6f795af69157 f59c99e963238da8962f2336b4ce6309 05b993ac6b622a29c62899af1587b42f 8e1f9ab6f1e24f3f9dfc55ae2032d527 c843cb4bb5b870f2f4b7c1c90490f906 cd1ae0b5cecfdb8147eab9a454609310 65f5c4c1d8d95d0f562e250df5d48c3d acefb2b7d6918767a8991ece3c818537 540aed038eb749c4451589c57762f1a1 257ef30e007c74d098efddcdd3fdbe04 124b433b3c1a6926a0fe6dd0747b023f 1069514f7585a98295456e7665901625 2bb133a60e10a934
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 34 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 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-08-22 00:11–02:11). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.