201508271801 3inhuh
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
d71ceae97d2cb30953e2a307afcdf5b9 de5ae3a6177e32b1c0c3b4ebb7f9d961 1e9299ec13853ebe1da414e7fef12834 1d61cde10d0834dbbecb15f35dc524da a80f7f49e28a24d7f4956979f2d97f9d b0b0564328584cccff405390a999a62e b577df7003841a3b3b0b42aac01de067 4dea8c296a552f9f1b72c6cc8a689bd8 d7d5530d3deaf0f1623d393fa8cbb87c 64c1de7ab6936f42404c29319b2ae915 16d2c66b2340a234c9682e2d8808db42 3ac3c8a3c90be1c8fdeff0d7dcb7434b af2da1175949ff4568d8c319964a6337 0021243ca9ee455f3065e5937d74d8e6 745bbab351124ea898e4e3e4795272b8 386cd087d73de02c3bccaf197e550d9e acee46e5e5f405f8977967319801e477 88987011db1f17d2acf26b814adf4755 a58fe5f0df16d3709d3bd71fdc26e05c cf82d710e9bbcb37c98c3d9e2ccb6d8a a013c0c1443d913e977e82ed34010f2d 7dea9e79a40e817bb00e9332a0468137 70078126f47fe7eabad195604a7631fd c0af81abfb3c1ded75a6e2fed0c2d4c9 5901ddc6d3b0e6f64c627a056557870b c1050ed93a64372ef042abeb9f4a017b d022548af31e3c81ab376db6f5c7154b a92f09cb1be5c55a6604a7f6d4ddc250 8f00b035ecbc6597e5c5fe5e96ed43cf 3976349dd31810c3f246469bd3347b73 d24f3213a704436c60ed832efcf42a98 ac47d1b5d065f00f614508ced5d656e9 3324ed0627c58482b2e5350f8fd69d27 1906b60c01fa2bfb545a87770565f6b1 647e80baf134cc09
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 27 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 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-08-22 00:11–02:11). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.