201404082120 22kn64
inferred encrypted filler
N=3
From the post to its content
As posted (encrypted)
a3783ec98aaa5a8a91f7f64f7e13f5a5 d59f4d99a7b8b5d8b0c3305e57735ac9 ecb9581b23f37435839a8d7444edf1f0 efc7d8e0a8b7f4ea55b20bb2daf9079e 3d77344533ec7587efcfac9c5fa0c67a a930e5f57dadc3ab43ad1f6d2fab906f e0781f03b109ccd5
Explanation
- Read the length. 208 hex characters = 64 × 3 + 16, i.e. N = 3 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 28 of Run 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) per post. The RNG predicts N = 3; the post has N = 3 ✓. The seed is the machine's uptime in ms when the app started (boot F 2014-03-12 08:00–09:06). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.