201511280020 3ujwu6
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
2b81e5b2ec05684f2c049f4b0a2a92ec d99a14ce8b5fc4aa11bdd34ff0490811 9ffb567a4f8c49df4eee293ea22a74b6 23f4f559de4d10e1fb94d07fe380a58b a59499fde2b8077d357291e7b8c5fa25 eacfb1eace8b72f5dd325b2e09e2f782 70b1be1c1ffb8bb216429c9f402b2a55 fb93f4bca3fd0545c3fb2d7f77e54204 fa5a6c63027921f0c8acb33a6aa5d017 57f8d9b5f4d9a61dcff74fa2632ed8a4 66b6f6a7e8f967484cde41ea9a7b7457 6a0cfecc3b44a6d0317b75906adcc4a7 3a06041fcd414fadc9bfc82dd93d9ec5 8743eeb2075337022d0ce20153cb68e7 a803e906261f81845f3ca6de3d6a9170 7de6214e2385cc4819ad13b4da6da40b eb0ca1d26689b8c90203ff0b7e57a156 d08c184ef8808cc94c1b548d6724ad06 4f22d1f7c2e7fb0648d1cd339f7bff57 e4851bed17fd39a52758b00ba8ce3215 08d0dbe0f17c89941fb4742e922d6907 25e0f4ec0ddf7ca9d334ca3fe8e108b6 353014b278e0d5ea7f812b7565afde53 842079a3a952b69307e15d133f6e6879 11bbbabcde6fe08970d226dec3184eda 27c55654e729c802ae997c5f419d8185 b3ade1968be328737b5acb000e941c31 e94387ab5037cc1dfa91963df5212b33 f912ed7650f352c6e1fab941ecd5511d 316c1e234f1c8592b29e0686a6ca019e 091c803f9c7ce1c8e9e3c071b035293b 1ab354c33da412d52589a3a902141cb9 635bace35e75ffed3f9eea6b6c2c6585 d6b3454c398e8102362538faf02590c7 7716fa0db6d8d28c
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 591 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.