201404081656 22jxrk
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
cbf063602eca4bdc0c5fb6f35b50ff2b 20a09ad90ca546dffe55ceb69505ec90 f0e81d86381e89b9b16940f1a1f60b73 9f36724c44b4dfb48c1016d49fe36059 3408c411efa599458f9ec43b53a60de0 c6c75a4df792234f2f06bdb13985d852 6b36967e33cdccdcfeedd7c1278e62c1 180046fa90eaa2fce4f8da7e877d5af8 da6a9ca9e444e7c1af6b48d99233e991 27caa1e2f92ad6b6da04abe86eb7ddbd 1472e45ee461ef97a74edb220a69750d 583ea58ed1821e04bb494ab5e04dc3da 36d6299b64c18073d02877e4e954fca3 b8e1ce5e04d9b27a131f39b6461a4f10 a3fc2cef9e50efb796d9a1f076a594d0 31d54166e21e2c3f74237b851b99dd7d 23a8b5e0d45af495aea7a9f93fc1a87a 2657542b2cc13b4c5649607be562e864 866ff5763110518a5a64045e977676b1 d3fb6dfffdaee11eba6613547d44f5e8 415132bf8f795b7c8d62ea00997a82c8 dbe45a5a3a72244d37f7c457e1300fba faa166519c69a1aa7b2c0e96525418c8 b334ad051beb7fc7f63c7a77634f7d8e b4c734a7bcd0ad9a08aaca61c2d93678 130bd7db57801a4e8e54d34fc233f78b b90479576fd909f1f38b9a00e6300115 430a97a8c95ccb38a47f77b82cc74d8a 605bbb7c7952976468c5a20adba8abd7 ad705cc68977845b50ad6afc8de3a7f8 481104be8ecbdc78dce1d8bf8868e4f1 481e7c1e6b32d7ce1aa4cbbb5e39927e e25ff5649fab60560b761be36c494ef9 1bc977cc2c7182bf4815cf366b998f41 42b974721326e781
Explanation
- Read the length. 1,104 hex characters = 64 × 17 + 16, i.e. N = 17 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 61 (seed 2,007,067,968):
new Random(2007067968), Next(0,20) per post. The RNG predicts N = 17; the post has N = 17 ✓. 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.