201508292201 3iwv1z
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
9f6487097f365ce60ecf345544802240 0f7876c332007a3990e5147fbef5ed7c 3f51d373ee6bbb2831c62501f8913a19 901205cc7b5a89a6b82f51f517c2fd8d fc3f9acda15da50d20c0107a1c21d43f d9a41cf7d24d6272d1fe6da2f4da4499 81a3630915e9f76930541d863c5121a4 cc523ee841a4a0af9fe824cfdd3363a1 a6d977d7dab3a5b051bec6bcfe21ac56 e1548c203f58702a586c99d000f4eb32 bcc6c789b66aadeaa0525179d756f47a fdbb018ba344635ed4f29f9806badb10 1c8edd95a59f489f3bb22bee942aa7b0 eb33b48cc5485a5a145bb41e5b92527b daeb2553f1e94373
Explanation
- Read the length. 464 hex characters = 64 × 7 + 16, i.e. N = 7 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 53 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 per post. The RNG predicts N = 7; the post has N = 7 ✓. 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.