201404251129 23xvot
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
ded358055eda93e7d1ccd63bb6e6e24c eabec145ba5831a8482accb7f138c630 a0aedc1b897fbf2853992bcffa929698 724d385777495563175c613377933171 e4e608ea80ac90a9414b41e1f8f424cd 956dd510a11a6664a1aa5d00a54a8dbc ace5779a7072e40608f2c53063136f37 5e818cae7444cdafbd697f3b3618a240 dac35302e13dabf5a6a45069cf23d984 cd61ce1813fa875ee3243e3475bbfe7d 919a84d27f4a2b620bff0b37aad57da1 23093a4830eed36db0eaab25b51cec71 af9c5fdfafad4dbc
Explanation
- Read the length. 400 hex characters = 64 × 6 + 16, i.e. N = 6 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 220 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) per post. The RNG predicts N = 6; the post has N = 6 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-04-10 09:27–10:27). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.