201508311401 3j429i
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
fd4958974a9850b89c91558a27eec85e 46ce2dba9110137d93e85c5e488b3096 82e9da872d833906cc2061d8ead229e2 b0a452de37c615b608f98d4c101e982a 8ac1611f150feb131ed6e01744dff791 43e4ae53104d47e6f9dad11f12088f4a a9363a82f365996326afefddce9ba058 b5e7f51bdf623da526c20e2e8a7831bf 33fff315ff4dc1c8853c25060e27f2ec 11f562c655109c8d51c2ecf9014541ca dc1bf07181b77fffb18729b16042d219 e0fce8c6960cda9a2e44d7a5567419b6 08b04855a77c42ce
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 73 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 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 2015-08-22 00:11–02:11). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.