201406071359 27jniq
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
e77449244698c9c562b23554cece61dd de54093c547bc9cfade3dc2590da0652 c9b01fea4c1240ec2ab6f4bb7fa16807 197ca298caeec33daf1a291481e2db77 94c9d4077e82f05a924b7fc8cb37eea3 3fb31aa3eae4c8ed82bdeae22c5c856d ea7ffdcd53508504ee3b53a029801b9a 38f0b93922ae276e79d7153196b25b29 82fd518719af7474c16631b6cc95ce99 321469e9afb787fcb9ff9673f07344b9 1019bd03bb5dbfeaeb738737b99f77dc 30abf460ed80ec45c304f825558d47c4 8c2cabea08dcee16
Explanation
- Read the length. 400 hex characters = 64 × 6 + 16, i.e. N = 6 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 58 of Run 65 (seed 1,582,093,843):
new Random(1582093843), Next(0,22) per post. The RNG predicts N = 6; the post has N = 6 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-05-15 09:31–11:31). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.