A858DE45F56D9BC9 archive

201404072243 22hlbb

inferred encrypted filler

N=0

Metadata

Post ID
22hlbb
Title
201404072243 → 2014-04-07 22:43 on A858's clock
Posted (UTC)
2014-04-08 03:43:02
Timezone
UTC−5 · title 22:43 against posted 03:43 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 61 (seed 2,007,067,968) (seed)
Draw
1-9
Machine boot
F 2014-03-12 08:00–09:06 (seed = uptime at app start)
Sources
community-archive, arctic-shift · body from community-archive
Links
Reddit · Arctic Shift · JSON
Score · comments
1 · 1
Tags
post-cutover2014Undecrypted filler (fits the length law)run: seed

From the post to its content

As posted (encrypted)

f0bb6943914a961f 

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 1-9 of Run 61 (seed 2,007,067,968): new Random(2007067968), Next(0,20) per post. The seed is the machine's uptime in ms when the app started (boot F 2014-03-12 08:00–09:06).
  4. Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.