201511280610 3ukppw
inferred encrypted filler
N=16
From the post to its content
As posted (encrypted)
041bc0f7d75719deda83b2c6a52c699b 513fe47a7577901ea455671d834f84da e080c6998feead6a62aadc430d6e53fa 47f80d99d0a0a2831f4d25414ce1a381 69ce482cf848e922c6e3843c3919607b 0468bb3cd0f5d9358755e5ee496ef8e1 c948a43ecd563dbe3685ebb55b0449c4 aa2bbedea0df421cc60e9630485de413 a5cf4c0e355070146886e33f2b1fcde4 0f62efa058159cb413e58e12f1bec9b4 bb0d1c760979e55c216bd00635ec7e1d fa22ceaac25c1ac7f8ad6f0cc927c2bd b58cd3b99dc34a5ea14a13da4e3e20d8 414b10168c07ab79621dd958905c3d72 ffae79a35875801e43b919f2b30de5cf c46fd8ce3e43ba34490472a3b1d90140 3b6e5152775d081c16d3f67c8aeb9402 c2783c74c2c87401d79a69f8072e0b2a f182bbeca084b44f3bdd7406b1c42661 6c4c8d6b4536f086f89604ca09ec55b3 7c01bbe8009149dc49d449bd0437f3f0 4e518a7ad5ecb3b61450e3251d21df75 a7b2a87b95f7ae7826e26b4118a5526e 69d69ffc38a435e382c0c6fa1d2b4939 335d2dd92a9f608c2d538cfd56d2d482 0f1fe3342d786084fb18b760b72a15e1 383b23ef9040a601f0e08ff1c0409ce2 d41016e7bf645e326297f81f75c8c781 6150cd436c29f12765048012359154b7 218e3b6b85b63b6560d630333e19a813 998d051bbc832200ada94c6561483e18 ec0ed131a9a8c128a141b1a129298e3d c2edf5f54e4a24a6
Explanation
- Read the length. 1,040 hex characters = 64 × 16 + 16, i.e. N = 16 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 605 of Run 70 (seed 6,038,486):
new Random(6038486), Next(10,40) per post. The RNG predicts N = 16; the post has N = 16 ✓. 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.