A858DE45F56D9BC9 archive

201404200929 23hzjm

inferred encrypted filler

N=0

Metadata

Post ID
23hzjm
Title
201404200929 → 2014-04-20 09:29 on A858's clock
Posted (UTC)
2014-04-20 08:29:59
Timezone
UTC+1 · title 09:29 against posted 08:29 UTC
Author
[deleted]
Account
A858DE45F56D9BC9 main account
Subreddit
r/A858DE45F56D9BC9 the main subreddit
Category
F5 filler by length law: 64N+16, N=0 (empty list)
Size
16 hex characters · 8 bytes
N from length
0 (64·N + 16 = 16)
Run
Run 62 (seed 507,820,296) (seed)
Draw
98 · predicted N = 0 ✓
Machine boot
2014-04-10 09:27–10:27 (seed = uptime at app start)
Sources
community-archive, arctic-shift · body from community-archive
Links
Reddit · Arctic Shift · JSON
Score · comments
1 · 0
Tags
post-cutover2014Undecrypted filler (fits the length law)run: seed

From the post to its content

As posted (encrypted)

fbf1ae880534e348 

Explanation

  1. Read the length. 16 hex characters = 64 × 0 + 16, i.e. N = 0 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 98 of Run 62 (seed 507,820,296): new Random(507820296), Next(0,55) per post. The RNG predicts N = 0; the post has N = 0 ✓. The seed is the machine's uptime in ms when the app started (boot 2014-04-10 09:27–10:27).
  4. Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.