201403182359 20s7t9
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
28e8e83f9a0d0f76699bb04d3f7739ca 69f73d6f1b2899643911a9210959110b 512e311c53c18eb05007c28dd14898d2 de9577cd2a55638fdd57b1938687a022 807c936553b75b79a087bdd46e27c5df 7c1633c75d010df2b3dd6867bfb8ea3d ba99810a0b3d19e6c4a2ccb72f3aebc4 0d1d87b0b05a97987f4c4bcbf03f5f40 368d840967ac20cb5d1f5bbab7c009af 9da99944071e0802824a54d46374417c 63b6f9eaeda8ad1184a93a7cc6140e6d 0c7c3e495045e7215cb7fa2ac37b54a1 53bb0af463663ec16e5eec8f554497f5 fb1fd3324d3e2f18aa500fe21be50890 03ee7b03fd8ca9a1
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 79 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) 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-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.