A858DE45F56D9BC9 archive

201403101859 202brr

inferred encrypted filler

N=0

Metadata

Post ID
202brr
Title
201403101859 → 2014-03-10 18:59 on A858's clock
Posted (UTC)
2014-03-10 17:59:57
Timezone
UTC+1 · title 18:59 against posted 17:59 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 59 (seed 1,704,050,750) (seed)
Draw
34 · predicted N = 0 ✓
Machine boot
2014-02-13 08:39–12:39 (seed = uptime at app start)
Sources
community-archive, arctic-shift · body from community-archive
Links
Reddit · Arctic Shift · JSON
Score · comments
7 · 0
Tags
post-cutover2014Undecrypted filler (fits the length law)run: seed

From the post to its content

As posted (encrypted)

a9d9c2358a0bcad3 

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 34 of Run 59 (seed 1,704,050,750): new Random(1704050750), Next(0,36) 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-02-13 08:39–12:39).
  4. Conclusion. Filler. Structure and count are explained; the GUIDs are presumed filler like every decrypted post before the cutover.