201401010032 1u55ys
inferred encrypted filler
N=4
From the post to its content
As posted (encrypted)
3653028a9ba44a926f55d72f11d5c946 78a0c5a6fe42c62773e6f48dbacd73ae e129c367da52dc862c9a85599fe0117e d6e620ed0c2130647ab2577c0666f715 d39c003a499545198724ef5228cddf63 441ee1b719a86925d81e60b7fefc1f88 95adf83df46671d7126d4868e55d4372 f4c4d2e29130bf3e024ce0562cabaa56 cab37e128cb2aa3d
Explanation
- Read the length. 272 hex characters = 64 × 4 + 16, i.e. N = 4 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 111 of Run 56 (seed 561,089,375):
new Random(561089375), Next(0,98) per post. The RNG predicts N = 4; the post has N = 4 ✓. The seed is the machine's uptime in ms when the app started (boot 2013-12-11 20:41–23:41). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.