201404091349 22mmpy
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
72e25f534c8bbe3f1cf2a08fe53fe614 c6cab2b8638695ff442976d19c0393b3 1734adb54b4069e4aa0b8efd7147f387 48576b832c2cd2e9bba2e68637c4b206 db1b68a0d7a1e65a1c40237725fc81da a0686b100801a3d9b0459348bc3bcaa7 c7fbab2e4b4e55dcbf71c2398f4a21ab 61e0a89f68f966052025e92996ba93c0 8b06f4e925d830579f210129fe4a0a7a 976e02237528df60d41aa70a16769327 77073a5797dd3b6f
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 43 of Run 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) per post. The RNG predicts N = 5; the post has N = 5 ✓. 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.