201511220302 3tsjx5
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
ffc1776660f6450ab9ec8e70d9bc80cc 6c5529a3c867d3eeca5c7610a488c28a ca7cb94649b17b46b6527232b8f66a95 dd0e7512df41e5f37b1149f41c36314b 1eb39a3126f1175fe11c393f2fd62479 8177460395d841bb72e3806b11bb28c4 705d5639fb07a0f097e7c3309a5c6bf9 4bbbc3579dbf7cd598760cb9da046cd9 a98b24a7917c689f86230b2246035868 b0046b05a896f58c1db81f7bb1675c08 c2ea9bf3482cdcf97d93e53556db3258 a7411c9fe05c79f593d0e3bafea0199e 66f9b1160088a4a58748390a4ba6d3e2 f14f9ffd3e2b48480791ceed10f2bb5c 8b5ec8e2bff4ccfaade1c22202375dc0 f91b2c89a700d37fa4a517b0419b360b 666ef4b7f9f5971f702aab16c335bfa7 ad6c12190f6f14d46ed0d31d649629fc 7781a0c9653502aafe844bccc9fe9008 a1891fccfd553e3c6df87d3e123cd7e9 a4ca102cbf946dc5dd54830642e8ebd0 62ba3d97ac166de7a01b4118df81cee5 0fa5fcec7f9e9d32764020de050537a0 1caddfcebededa9be25436bd8e67f827 fe634a1d9f36a386bc0c68776b0b1fcf 160ae7b74b2586eced4398ae5c17898c 578c7afbb4588c8a628ea5bd34870147 704bcf6c4edd03b4d2bc26576f2ef7fc 61abdc731b072864f73472251f34c036 16bb68a5566decec706cb4bddc4bd78e 297ba89dc5812f26632f28a0bb8116c0 74e18e19d723c71baccfbd8782177bb7 8669890785a116ae29f70918d5eac950 2e2735da0b3ba8d1dcec43c876583c06 ed859e6974224c1d
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 252 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.