201406101759 27ssmd
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
28c0f7f0eb8a4cee333fa2ff9c0840ac 029cd5fa3226dc120b299f42a94c63af 5250144841ec59a1f8c3f6f90f5cd0bc 429e528814b2cd74b90fb19b4adbb828 83c8a251121d07cff75e2ad965fa89d2 df6936dc8089d87bce37b41fd7fa5ce3 63915634c001391d385285829e067bdb c22961f5b4e944859ed275eabfc3b374 573ff19937723a0439c4d9926dd9343e 363011b1fbe16a319c3d9dd171c5ef0d cd302be34dc819e3
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 96 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) per post. The RNG predicts N = 5; the post has N = 5 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.