201405131559 25g5jw
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
493305bbbd7558db74bbd271b06c7903 4422b6ae7a176c557de1e488e6503722 601ab29c01b6e77301564b9737551b98 4b824644b15a8165b311ccd1df0865c6 a98fa5895e69c7c0b68856201f69e21e e25fb4c1a7e32be041de3658150663e8 e7ccbe3f825a4f81928e2efc3a629727 1450029f37c1920d4877e945a59d0d5c 439ef26a95fb44c3fd68976653b98ea2 9baf9bbc8a2bb450628b6bf88af1ba8c a4da7731fc56f925a0d4e6af63114086 1abf8c0a50e168593e19aeb3cfcade59 c9ff3f451b33c532341b5cab053db84f 7de6ae4f604008efd6635d41f9e30c0e 198a95ce523d06a5395fed04e4858f25 84c6579ca823efafb8e5d1cb32523ce2 723e49f6081a15a179b7d9968d4ab0af 1580012fa8d7db23fbafb8c32f62c6cc e927183412cc261f292e6f0bff58c5bb 7ad52bfd6eed259aac5a981a370fcb24 b836e0381a5e0ac77e12f013fc2e3357 6a3d1139b93d382de57409ff0b9e6743 72744517b2ec2cca6b38fd7f22131266 0e06e2d1f5a006d24d0b20443064e73d cd66edb66d6844c79ba3416a2c0d370b 4ce6d33193c7ef5aada68834d4f8ed7f 77e415268187a9c0a8082b656de0483d 5911de12b05cfaa161bd98053bad7bf8 8942b55539a29836ccac21d25325cc64 a67819b1358717b963821a96c2ad181b 2d56f062c6ef6cdf0ce736116d2d43c9 fb1fb537be48d9c1fcd022c4f770b20a d8b0c8503de7d24022a306b1a12295c1 b86038989565e03225ac3fb03679d36e 9ae2c7db8066d7b3
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 19 of Run 63 (seed 1,506,676,046):
new Random(1506676046), Next(0,33) 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 F 2014-04-10 10:33–11:39). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.