201401072132 1uof18
inferred encrypted filler
N=17
From the post to its content
As posted (encrypted)
6b2e6c657a41b2c4503f4acfa4dbfc77 8b203a75e92dd7f004f06636a6312669 ff1df3ef56d490300c4eb6b068b3c9a4 0dd8e93e3277a647fa608761b963ba20 3f5eabd670c34000f4d0b986c21a05b4 b4ab0354b389299453b430cc172ade43 21995e0a04f17d4dd332eda76bff7258 2b55328b438949ec59f6b39d753c06bf 35dae8fc2ff34ef69204d16916112755 d30fac87e6c7c1df08e5f54644e00fa6 5fb2edce935c9946d9845928d52b40cd c85a7b88f993179fbb31a96f3d128cca 94f91ff776ecd71f7162e37682f5b2f7 4a08efff15b73e1af8a0ad5510f073b0 4aed23ad8b75448a4d2e9c5e14da02b1 2a2f0d0b1fb7b5c7c0ea860922c74a37 b7b5c59325be357193438f7fb8d06e1b b54653eef540df7c66671f0833d6051e 2d7ac5674fb591a2865bfd82ef63b238 7e1c01ecdfbf6c20bbb7f8e7cec374e2 1172dadb4ad1588fa583e4cc8f7a3169 f11cece6ea86698a01e3ad9ff7352e6e 712cb76d4bf82bca468c72f0164640b5 566bfcc5fb8f199aac7a0be2e8fb9fe9 6b9ed6f3999c333f81383742c37edba3 349a42f3594e480af325cb3f498fb65e 75c6cd3a8e4cf46dd5e5d2c8f0a660f0 5e7166a15b5262f2337ab1133e33ea1b ca3fca3ea195d554d3978413ba797512 f3dbe661b2594e987aa170eebbd7bfe6 87cf2f75989e50887f034aa575e8c2a2 492394177c135fb9c6d4e48481e4795d af99f224acc8755401990030b0d5c641 72a55e16a05e5ade362b7234256412d4 0b90d19bdf858d08
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 166 of Run 56 (seed 561,089,375):
new Random(561089375), Next(0,98) 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 2013-12-11 20:41–23:41). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.