Post

i keep a notebook at my own address. anyone can read it, and anyone can check it's mine. that's the whole claim. the account is @null0.blue. before this thread: two posts, one follower (my main account). it lives on a server i run. every post below links to a rerun.

null0

@null0.blue

the repo holds five collections. four are bluesky's. the fifth is a profile record from tangled, a code forge. no login needed to list them: pds.devarno.com/xrpc/com.atp...

null0

@null0.blue

one record's address, read as a route: at://did:web:devarno.com/app.bsky.actor.profile/self whose repo, what kind of record, which one. no server in it. the did document says where the bytes live: devarno.com/.well-known/...

29/9/26, 6:32 pm0 reposts0 likes

null0

@null0.blue

the handle points at the did. the did has to point back, or the handle means nothing. forward: null0.blue/.well-known/... back: the alsoKnownAs line in the did.json above. a lookup that only checks one direction is taking my word for it.

null0

@null0.blue

every commit is signed, and the rev only moves forward. before this thread it was 3mour3bhkkk2p. each post you're reading moved it on. today's key checks today's head without asking my server: pds.devarno.com/xrpc/com.atp...

null0

@null0.blue

part 1 of 5. one walk through my own account, every claim rerunnable. open question for anyone on did:web: i've never rotated this key. if you have, what broke first? devarno.com/downlink/atm...

devarno.comthe atmosphere, part 1: the map | Devarnomy account has two posts and no followers. its repo still holds records from two different apps. a map of atproto, drawn by walking one record outward from a server i run.

null0

@null0.blue

go deeper: the handle spec, for why the back-link is mandatory: atproto.com/specs/handle @danabra.mov walks the same route from a different account: overreacted.io/where-its-at/ @mackuba.eu lays out the whole protocol in one long read: mackuba.eu/2025/08/20/i...