201511232337 3u1ebj
inferred encrypted filler
N=16
From the post to its content
As posted (encrypted)
975eae2f04416de275c8bb33659f9dd4 0ce367de6c6270bc4a28dd5ef92c3fa0 6c4c1efa08cb13f6117fa84bb2956e5e 91903f65f6a222b3ec405cd6b1f20af5 edd4bfea8949c40ed250d8a52d61a356 d46a0be6397f85a07d683b9bcd04fa79 1bb39329843f2fc4c557888bff814027 a60d66b029423d52fded470c71487765 7a6c0f31c4d1f49839fce5403a45fbde 82c6ca33d50ee460e1a782075dd951c0 d668bc84a890adf3c68a2f02b580c3e9 7e38d47e8efd575346e41ad108ce91b1 8291d4247b9f73a818c20535c0cd16b7 96d00c731eae73857609ea7fa5cdc50d da867a4d214f764d060503458fcec8a0 af2d9d2329cfbf201180c636fb62a037 db57f5575b5e6c2f1b0fa1bde9e855b3 86b82f3ac50e7c35e8b443896b6c08ca a469f74e680abf15c97f9289bc6680db 175146c05e164f38a20ac0dc60c5e1da 64774b9d58e8d86747f4c6dc377fcf47 9df732c53d0c1d8351ea21dfcb374681 0934b77cb6cdcebdf6b0503090dac692 3617ec200a7a39c27e199a7c733d8f0a dc31d7ec84f79b9cf97d60d53aaf5ae6 a20798d1f72b7b69956d93ae4862d693 174ddef437518a97a2a9a0799e00bfc2 4a3cbb04906147df6a3f92ce614359c3 6e3a75a4680111919980d7245f583e99 b31a994676e02b1ef1c40de96959f772 422a59d83e5abf27bf8c56d34cd2919f 31f3b7c7f189f0772d7d0480270d659c 58fcc4cef9a4afac
Explanation
- Read the length. 1,040 hex characters = 64 × 16 + 16, i.e. N = 16 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 359 of Run 70 (seed 6,038,486):
new Random(6038486), Next(10,40) per post. The RNG predicts N = 16; the post has N = 16 ✓. 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.