201508310001 3j1jwl
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
17c42dd9ce311fd2983fcfdaa9bd680e 845edfa6b9f1f610c009b8404eb2f7da 1afbcc3143827099a494d3124f3338e3 d522dc50310ac5d696a4a68613a1d549 69148927f56df02fefb902ed65e47f50 a645a4cf29305b5c6e3e4ef2f924e923 b6a535d7ba7ab6bf6e979a06932b1114 4cac7472bd9ee863a410c806f370a1b4 c90faef002aaa790636248dce300cd88 5f63abb869867447f79ca9c8f87908ce f94ff5195b66da3dfe96086804a855af 88dca6381d974e3c34188c0ef0721c5d 3115218bbffebace9f79f3052e74c3f2 f69cdb5687abd9477e2156253a7c4725 56e8d9e8a38739e011b27e03b0f95418 b04e5073fe0fa9898ea094f5f28b6cc2 8c3bc71a339e6ca72a96d6e11509a2ac f6da752ea1e64e1e088045b2934f5c98 49504d4ba3f957a74ab75ff5389d84f4 ba8392bcc3b77848aa5e913e522652de 96be75848193c57603541f12a2f26198 43693355416ba24a03c4a5f662dded6b 4ed433daa5746e5ba333817560b0ef33 77ab9f3924abe8f41689ef57032d3f65 6be234315f438c1c21e419f3457e318d b86d28d3f6329a15f6fee20cf51b65b6 ad50898fdaf297aca9d0afcdacb44fe8 508d38ffae576612ad07f503e59203a1 5d34dbd82d1634cb51521a597504d5ad 0604047ad54034f00a02647ff8561e5e c88cd70866d308888c0b25dc4479009f f4fc03c250a2321421e3533c933e2fb9 0ba5c19b76743b40b7bd9a9152da424f 810054503d960b976516c7c4f0be9474 b98914f03c10f636
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 66 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 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-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.