201404170730 2391k7
inferred encrypted filler
N=6
From the post to its content
As posted (encrypted)
2ea48b1e58efce20c52f93fd5bd15b21 9b0b737348c1d207ff23547013206e25 e1d40d1178357770cba923412df82c9a 5a8dbf5773b3320402d5007d052b6f08 706abaccb3aee0767a1a1400fcefbe7c 42b69c41aa5376c31f57a5b36e466200 c98a28c3ec727addb2cff4974805f4c8 fab84f105d32c94ebb7b2182be0430d2 483f8b69ec646e844b2873f935aa8a4c e1cae7980e273921e8819dbb41f0d2f6 a7b0124bcf71573778809b608cadef3d b85f901c9919e4e3506fe352425275c1 8208f90f65f92fea
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 24 of Run 62 (seed 507,820,296):
new Random(507820296), Next(0,55) 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-04-10 09:27–10:27). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.