201404161830 23732d
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
b0d1f28faff20b7960bf4a8454035296 d34c0ce68fdf7274f5295fdaf9df5bf9 b2aca3f6ee4f89ad459d14d18179ada5 757a812fb8a643697a0696f846a6c9f8 80e74aba742d7f155d1efa455ce95356 c975868abe8916e3e8d4f290fe955b3b d0dd34f3379123578d63719497684549 00c2c5503294e33b361cb53509a31537 07d689de53705835d7dcb98f7ef6ff52 96fbc58c133a462a35c997f9c2617f83 d96e3c135989f13613531e2d0f3f19a4 e6d3ed9ba485f889b768987aaeab5bb9 31ca813ba4080755
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 11 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.