201405202233 26355a
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
64bd64f69ee51ab8a57305a75e652fd7 b0616c84dc4d8a771f42f8949af2c956 462cbc95a8a861cc335c9daa67787001 5e012e8cf3bea7d56330d620acdc761c f13a4ca45a2919772b02310fd7a86362 2efeea339945a6e67600bd13dac0ff2b 8bb41c26f084cce44069f6e03d3026e3 b0008efa743ded9806a92826e5f9e2bc aff2901d783323940197c76f72453d2e a75dd7df258688a3b9ebb48fe3d67218 07891cb8b98ca8d1b620628318089044 929203679ce40c88c7072e7525c4ae16 ead7dd823f53b207b4ab79dea8ef36e9 85b324302c2f0dee03190232ae42918f c5b7b3e2c3418bff
Explanation
- Read the length. 464 hex characters = 64 × 7 + 16, i.e. N = 7 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 35 of Run 64 (seed 367,071,562):
new Random(367071562), Next(0,33) per post. The RNG predicts N = 7; the post has N = 7 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:35–10:35). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.