201512060000 3vmlwi
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
bb09b9b991c33e2f70641aa68cd29842 7b06fa61934f0d42c2ff617d999e740c 3dd3018a11f19810024b13365bd0035b d6fbdb7b46b0d9c077ecdd6c30518a49 e42a7f2d00d039302c80a48177fcd888 3a30a320d8d1f1e38b9307fc87b6800f dc2c41628442df3dacfb395e5867ec8b 53967c144900d6d26371c386233d7704 ca8635774d2b13224cfa8f4d11d10f07 dec58feb1d5f25b622813e8059507dca 7885f7c1edc9dba1f0bc43e6ee1a4bde c8c677fa4364371114470bdceb0bc059 fa843f128643f65eccb2545f45110836 03abbe38cdb75987c0c806258ab5e5b9 501805331e4fd11d2ac4316e676a3585 ca8a7154f750d8f5e5838c899a76f7ba 5d948852119fbb6f507c67941ca7cb1a e3697503a7551df8b4c76562095238aa b99ad8edc88a962a8ca0e08f35adbfd9 bd586fe1e5841cde7c5301cb511c5c6c cb9672df46af3b7db24f0aef21c2d1dc 6e31441e223fed4ca647ac4ecad50fa0 e07936e4e0cadbf69e6fc28e76ef75bb 214c5f82cb6e81f66df561d1178e0eb9 fdd37d4da3f5aeeba86eb52c7f7bda19 7937c65d6aa0d31710ca6f80d7e98911 7323855a63930b9450f5da11f5f26b54 f1a97fa5502aac0e03dde95d0fcb4213 69812d56d72dbabdc9479445ca066c1f 9d3b4e8fd9543d110909e3d27baf9ff1 328ac54d1ae933485def2269d51c82ff 2d02bf4225e1c861406c91a130ab3c85 ab234f6c78164045fc93d2c68e557aa6 7c8928c6d087cc3c9c2e43a4898ce3ec 1913afb418baea7f
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 101 of Run 71 (seed 1,220,915,585):
new Random(1220915585), Next(10,24) 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 2015-11-17 20:51–21:51). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.