201403151759 20icey
inferred encrypted filler
N=7
From the post to its content
As posted (encrypted)
7fe668ba108a732c092b208c218c6980 d2d225b83546f95010f2cd00cd777aeb b0c57ab74cd30b8c10498d8b6e91bfba 4d19f1a134edc94bbb4764a36b12fefd 7a0888527611070e83ebb00cfc00635b 63f512abc863ea281918c51366aea563 9fc307f3213c82b87ae2d8c0029c5b95 ac0ebd2866ca88e0cd059da7eaec644a efff88309036c9342c2ddf339464bbd8 3815d255882acfd8c785fffaa57ce33e 3f173f814f57ec4be65e6e97f5e5444e 8ba734eef609dec591b635ca8a7709db 8828764f6609ed4ea306b397dfe5326b 0b951878752e2af64515e73b14767a41 0763e9862733509a
Explanation
- Read the length. 464 hex characters = 64 × 7 + 16, i.e. N = 7 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 40 of Run 60 (seed 19,858,187):
new Random(19858187), Next(0,50) per post. The RNG predicts N = 7; the post has N = 7 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-03-12 08:29–10:29). - Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.