201511191134 3tg8t3
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
e6c1315783a6463f533fffea16537749 89c6239fb4efdbfb43634cfd4728640c 76d5c3411a1e6b71a44aa51a362cb48c 5df424c6b57cfbe7ec1fbeb17f01b193 3bde4884cdbeb7acf527b4b1fa8d8fe5 ac78c3bc1c07d34c62800ae95f053bd4 d3ff1040d6e0bafaf19e357c9e626466 d2b03f3f54b5ec4a55b6c2aec97259eb b12350f7addeb611ba1e9b84533cc433 dbf06a286147cb14c692aa11ef367540 92314c8e668db4ff82538f598703f730 4460a478c58bae19d03b3e120e2b4cf6 d03fb7cfa9c953dea801d5b7a8da3899 570eff71f05a4eed1548e34bf56bd3e3 04688b7dd49dcdf1e2ec6b04fda21dd8 1f5a46aa86efc5d8bd5f2b36712694e0 d4520afe030a7df04102540c860f999f c815446bcb62d2c096430cbfb49d6765 43440a13b9a1de338978ac037135b571 d5f5be2505dde2d634bae2b80658b4d6 6d1b6446fecf02b4acb1c10ad38b0864 08fd2e177664c4a8788043ffc6ea6b73 bc34c65f020c7baae4e38a32ba6c7452 ed8cb49375d3c0c83bc68defecb544e3 41e93e141b50119cd75090a82f3eaa06 b48ca237bbf626e027dd2db6940ab52e 084797cf64de780fcdaced753d57322b 5f9009fb208a1f6110c57a52d147f0d1 bec316760652b77e847d2ac3ac23aa51 3128f0e1a6b86857f38031a15e280ed5 976484452bf31fbe40293d2244d9db90 b7ad721ca42328b95a4c1e5cc1bccef6 4a06d04bdd0d3e0148fca20c202397e1 362c0a1d19fa7f40f241dd6ea1cc4e8d 23131193b4b0e978
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 100 of Run 70 (seed 6,038,486):
new Random(6038486), Next(10,40) 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 2015-11-17 21:21–21:46). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.