201403252359 21dypu
inferred encrypted filler
N=16
From the post to its content
As posted (encrypted)
de51b49b4be5cd05b488dfbb641b305f 0d2f107dd7dbec85e98f6612b0533b6e 3de2dcb71c70887492db754b55e34ad2 b4cf7e3c03db6e23db3a9625a54c2941 d51637eaaa0f3adeee3cbb4ebb193433 49914903cd96f33db4d27ee693bf778a c8612818005d0680375f78ab4125125c d2ba62a30c5e0d628bd68671555c6c44 7ceb34433c2c4469a0aaccf7ca8570f3 cee76d0aee25fb30dfe493e526f0fac9 7eb319aa5ef3a1da0fbff9b40af80443 96646a92446a61f95f1e973ccde2dddc 931e4932c1eda62c13bcd6e90adcaa31 032f46751998ce8a2e3386a49d08ebb5 c2736e98eadc4d066b2c17f441ed0654 ed01be5262001994f22c652438993018 c9a38487f3312a6a26d01522cb032b8e 9d03072ec21554c618d53dce53c7eb85 a8626a1d8925901f5b0ebb5b0c26914b d9aa037f5c93c5a2290618b3d13a577f ebd55d24edab9cb857276f979fae64fa 5b2bb1b0bda7e6edfdffc684df475b6b e1c96097046fdf5bd9c1723c0803caa6 eea53cf5c99de1c395fa9e8fca350acd e3ad40a8b9fabfe25eef6cc1a493fd4d 4e97a04bf6dbc9390b800d9e238ba66d 1c95694db176137c68f2f7fb0dbb3e6f 3c358dc7d37e5ddde9e9da68249a2b91 bddc0b5c62ad9bd3d470f669b432e8d0 af0a23cd91bfd5fbcdcfd905bc6c9ada d35a54e0c16cc23c1a3f021f2cd129f9 353b5ff8b28e81550dc0aba4588e67c0 c068974f8eb7af5c
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 163 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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 2014-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.