201508281801 3is2cy
inferred encrypted filler
N=5
From the post to its content
As posted (encrypted)
985e4cf4acd289fa9ed6cd1828630187 c56857251629431f9527a83caeca4ad2 9148a56bb6b80d639b706f341a0beb30 1be6cb99033bc0d7887efbc256dc140d fb8facf9718600a55614451d691c07db 37902c8689fb8ce4a500dde33c3a985f fefd76a3bf00eef34157a6878ca40175 6ff1eeff1fd069a03f984af9970bff01 5ed793f4baac8b252d24bc77bfe3a4ed bd5d9c77850ce4dde6da81799bfae00a d7730d407a9db8f9
Explanation
- Read the length. 336 hex characters = 64 × 5 + 16, i.e. N = 5 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 39 of Run 68 (seed 316,235,227):
new Random(316235227), Next(0,22) +2 per post. The RNG predicts N = 5; the post has N = 5 ✓. 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.