201403051000 1zm5ye
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
61b36b704234ff96a2e18ee91068a3d6 73b2533ddc9fb9f29791840183b235f8 8c6e12ac8ced584ee93a0382d9c600da 5d670ab34c1a1478c8f600fb06dfb6a8 3862ab3ace63bec3270de311eff8d8da 0cc1386161512c0630388cc4a9483a8f c12a5802ce2137a8f86307154e698e2e a1ebd37b29cce2e4438cf568b7bb2e09 41e4182451baad8e14752505ee874398 8e3d571a084b0f6f5db0202f53264ee4 58996a3716930d109a381bb334b81717 eefe0af5251c95dfefda29ebe543737b 50d83b9242a5f1d6
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 2 of Run 59 (seed 1,704,050,750):
new Random(1704050750), Next(0,36) 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-02-13 08:39–12:39). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.