A858DE45F56D9BC9 archive

201404090926 22lxe4

inferred encrypted filler

N=2

Metadata

Post ID
22lxe4
Title
201404090926 → 2014-04-09 09:26 on A858's clock
Posted (UTC)
2014-04-09 14:26:00
Timezone
UTC−5 · title 09:26 against posted 14:26 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 61 (seed 2,007,067,968) (seed)
Draw
39 · predicted N = 2 ✓
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
5 · 2
Tags
post-cutover2014Undecrypted filler (fits the length law)run: seed

From the post to its content

As posted (encrypted)

1b5e4d92e706619009f48ea40ffb12b6 b447d2fe62b2d11c63c50da12209210d 05f3ae362ab9c1120ec44fe27f377cce 4489916c399ded8b9f9aa6c680639b98 77cb47f68b0476b8 

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 39 of Run 61 (seed 2,007,067,968): new Random(2007067968), Next(0,20) 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 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.