201511261410 3udnly
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
94bcdb25f55f918526e647bb384ef096 55b0e29cef4465e1a373448226cf4fc5 835a92b5d5efa5c19aee09f98264b876 8c638b19bbd6549b831a2a3cc16daab2 d82a0cc5ec99fe38371adb210ab21b4a 9c1c74740f1d2ec3cd6d28abbfda6318 e8339e3bac1eead9cb9c218fb6ca8110 970ccbf05811a9731bfa4f1a56c13483 70dab0dbe74a42031be1af4c716af74a c139862d1c42b00885a68a6c631bf2c6 82be0f4775a588286964ec3476b5612d b0707ff789def053ec22fbdf997b90f3 e9b8cb0ccc39fb34c94ef509683b72fd c0c379881af1d5671a6c55008a9639a2 d0ec8a9f73812f6b86b59e7f65de4d2d 1801809d16e494c029c9584e2869a04e 2facd55781b219d6689e6a3106a24ecc 3e8f8d9a03371b256e047c8148949e1c b62a5e9bcfdc11334796cfc55494f54d b4c6a894fa289ad68bcf424c52e20dfa 0a2d0083df4192a9847791802ac4eed9 f293417562bebfe0ef9968e48817854d 29bffbe245d0f9ff552dd32bb6b66d80 3777b9861eb5285637b6b56688337840 6bd13affd61533bd33acad01a17608e9 070f2a79375e08e0b9d0e852cd90d07b f2c0477d433f6a78addff5ed2d0ec1f3 e558bfbe2b1b52b094d4e4b3ad870e08 e46b7d6c672cef454f3e4959fc786470 8eff9f756b1cc7477021d7ceab929c2f 02dea501c56012a857c8441458e9cb6b 71cfca75782410e05f2d40af65eb87bd 3ade7d1c43554f6f65ae9adac2f520c0 cf314110f6375a0a3ea926a252db8cc0 6db72970ad83a66f
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 509 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.