201403240359 217rpp
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
91ffc2e262c0eb959fe026f4379cb6e6 b1fa026af2368875a42898c92b4315cb 36fdcad31149ab9184f972a32cc62dc1 1a4a8a67d571a0a21e3711eaf3ba20a4 c66d72d68c349361824d8792d4bdbd44 2a4525146ed25e8a4601dd2825ab05e9 d81988e4dea591cd045a6aef07ba6fe6 f1c42bae7f41716e09f93815c5d38430 c3cf1d3cd14d74ef50278203b4506fe6 631a87e14084fd577315efcdda7e41d5 5310aee37ccd0fbec3ae9f71636f42dd cd0844e12b94504d49a2df1764c6788b d40d51cc7bac3dfb
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 141 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.