201404270729 2437ke
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
46aaec93f9555569b753a0b262336541 dbb64b39b2f423dfe365d65b8a451c5d c4595dc5a2e50d30aad1b52f47ff922f 0cb52a61bbf12b0408700cb6780b4b66 23b1cb27018ed12d53e783ae6215a5d3 72fd67d32c87003881785cfe5fe16bfe c8ff868f1cc949f7ac4de35a1da495d6 fd90d4a53ea63bfa9d489e104b680332 09a5225b0e7800806502a86ffdf0b26e 79ec19df68d42ffe7180461292daa111 fd846e6657e486f01e9ac64214a8ae8d 88c9e065335ac0351a591f2587a06896 6a1f2c93753a8ea1
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 264 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.