201405261332 26j9ss
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
4288a271497e62623fb4392973f8f941 ae717db88ac6ec937b27934c9269edb9 e7c4a4a1da0fec9910ca9ca65605a596 5c10b0346c938eb16508c33a4841fe66 d7b66616a6d133dde2446aa6410f865e 8c2fb593a3dd4e863ba37ff9f32382f9 b75b5328f9842db987cee3cdfea55143 29b0c6a9e9bdae184ef30e735e06335d 7360e7aeed4ec091223ea1f623ec3763 7046dc11fbae20ef6cddbf2ddf57c241 79c8b48e7a0ecef5d0ecdd87f5fea0f8 10150daeda933d02688ed5ffe94adb9f 8705c3ce78fa4d8b5c2fec495dae7749 3eceff09f0ee77ea1ac8f1129d65fbb6 a39bd14c487e374c141c18c8f18a3e17 1bd98c068855176fb74555f2e1c4b796 2338d55059423cbae4752d6b99771bbc 8e3a977bf233b31351dd9d438a2a4bd4 f2560a8dcebbaccc260bbbdbeb5fa8dd ae12bf01af2b304068920e50cd785d10 d8dbe1cbc5a93fbe6559716fa6bea850 f9bf46d8dfe07374932d3bfa674d0b5c de5b8f186917058f0dc9fe7b2c971a75 29a33e55b2824ba57666c6c2371c8843 a573997429151a38a668ce4951068220 f54d7d15b0848dba97b7608594f9f89d 5a3414403f80fb959c32abf13329c577 66d92b5856e2d6c21030919919438cc4 7858ea258ef03c06a554fb6c94531cc2 b2c5f18ae97003b51f9c629e4506412f 38325c5e536ca4259751b6ad9a9fe335 988687d50c20eaf3b8f4aebb571343a8 e4f2ef6ce80fc17527196a2bd9429d00 42ea15bd4b53d05e58347f970b7b61fc 58955a4e34e65f65
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 170 of Run 64 (seed 367,071,562):
new Random(367071562), Next(0,33) 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 2014-05-15 09:35–10:35). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.