201511250154 3u6q6d
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
848b8ea73e179fcb14c2a0f031731d31 380ba4ec65ca20d89fc6165b76ad19a3 1f852f7db19e79e82087ad6ae5823ec0 b6377dd634d6035c28181a362c563c5d 54010937b78dcee4ab6658e2299a3496 fd906bcc6dfcec23992d869d327392da 52cdd62bf748c755d7a22d6a1b35efb7 afc41f0ac61c638fe7dc7e8bcaa48928 843f4c1419099beb51b4f71c2af529ea 502e3bdcad5dacf1d0a5338858f57057 66e5d36e4835f0cfe6322cd7b009c486 ddca953100c10e44f4ec486d3d83b7c5 fb123e9c803c4bfdf68d62627af6ccb9 9074b7de0b6e9765460b470e60d35921 58dea3b7b718f673d16ba8983afaf001 9048755a03cf38b840ebba2d6088e04c bfffcfa8378c82028e900344563d54e1 e43ba96daf4b4cf71ec171ea0ba5a3a6 d65cab0c379c07c355a3670d368539a2 ecc42f068f14b83874d5dc6c7297cdd0 8039fea3997d715bd16c1b8a9e92ac29 0e0b226a45d0d5226397ffffe2d96787 46d74029e56cdc563f88605530dac3f7 96cdfd7ad93d051722dffacabf771bb1 a58861a4036f34fdae2c0e81be1189b9 2991a2c294bd6faed1268f3477aafd09 133c33be3ef85b4db4a6b9ff9d9d7524 5bc5553671fc291001b1f42775d0ddc8 ed6c8dd71c929cd172eb7a13c8c47c42 626fc1438c57c594bbf9d66f9e1c8e24 a507d16b05dd223b2c78df683fa566e0 9451c3e73c531684becec4965157caee 72584894d04664fc940d9ec8383caa23 11956ccef30a328a2ce159930c71a881 57e24b7d97a33fcd
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 422 of Run 70 (seed 6,038,486):
new Random(6038486), Next(10,40) 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 21:21–21:46). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.