201403151159 20hisz
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
69e720cc009025570325e1fdf562bc20 de166e52fba61f3ed99bb6e4f9e753f4 e9f6b10eda917d6203e3cb3e120165b6 d51b0f38273353d3fb2dd18a3d1248ec 7853a96a06c60576cfb69b9614bc20cc d6061256ca78451fef8dc9d5d09b4e8c 8a413adfa48ab3ab5a4986d2d7b479c8 7b76e09e2dec26bfb8ab24a1397e2428 a0183451d7281c45c958c33296d9944b 3228c33d1c2e802f7a71e912997ff02c 00f21c50d38261a5dcd8df2e67a83262 0a1dd9b572a8b98e0eefbdd2a3df3b50 2b69ab07641f18b83e1f1fdd15610c8c d569b2c5ebdcd806cb242f12cdad8833 ad1758ec1d9ffd35cc13676ffeaea385 e12978ac5060b833791e3fdc5075ef55 506212b9f9195110737d0fe3d6b0f73f bb14473ff22e74717a2a19d7646638a9 a112bf023e0b06d01fab7de0c2a870c8 e819e2935c079b41c34c2732ca410923 31ba00bbb42903b864fb976bd2f7979b 131f080becb80fbc6d84804d20662208 b132361b621d3f1ce36e51123e9d4050 dd8dab696e72ae97003d26c43cf36465 7d2cb28652d57d562e1ff1ca85c73e58 8928dc3537142372d32e75d6c8671350 4aecc5a2996be3d21de901c667ad5bcf e335fece215cf4ccfc60ba95483e3c90 1cbfda7c7b517a0ac7f4ee104cc5f2fc f49398bb18661c6e08c9dffe609537a2 937f8ce806976bbf501f91862ddfa196 eda926f79ca2fc31b0f12345b26bf0e3 98b2dfa2b5a31343642fff86d87ab48f 426d2b1584357f0c24c0a137f9d2a9d1 61cc71b7fe159154
Explanation
- Read the length. 1,104 hex characters = 64 × 17 + 16, i.e. N = 17 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 37 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) per post. The RNG predicts N = 17; the post has N = 17 ✓. 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.