A858DE45F56D9BC9 archive

201403150600 20h0q7

inferred encrypted filler

N=2

Metadata

Post ID
20h0q7
Title
201403150600 → 2014-03-15 06:00 on A858's clock
Posted (UTC)
2014-03-15 10:00:00
Timezone
UTC−4 · title 06:00 against posted 10:00 UTC
Author
[deleted]
Account
A858DE45F56D9BC9 main account
Subreddit
r/A858DE45F56D9BC9 the main subreddit
Category
F5 filler by length law: 64N+16
Size
144 hex characters · 72 bytes
N from length
2 (64·N + 16 = 144)
Run
Run 60 (seed 19,858,187) (seed)
Draw
34 · predicted N = 2 ✓
Machine boot
2014-03-12 08:29–10:29 (seed = uptime at app start)
Sources
community-archive, arctic-shift · body from community-archive
Links
Reddit · Arctic Shift · JSON
Score · comments
6 · 0
Tags
post-cutover2014Undecrypted filler (fits the length law)run: seed

From the post to its content

As posted (encrypted)

1ff1cc078413367aaacec55207dbaf07 8c754b15feb26b28908db94e1c0ff56d 9aeb597e3dfab786d40a513a7388a338 680a57c66c4864961bc6d8b44e78b717 8120f1c7c2a54f31 

Explanation

  1. Read the length. 144 hex characters = 64 × 2 + 16, i.e. N = 2 GUIDs encrypted with 3DES plus one 8-byte padding block. Every post-cutover filler post has exactly this shape.
  2. 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.
  3. Explain the count. This post is draw 34 of Run 60 (seed 19,858,187): new Random(19858187), Next(0,50) per post. The RNG predicts N = 2; the post has N = 2 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-03-12 08:29–10:29).
  4. Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.