iiinova — where your digital self keeps evolving

null0

@null0.blue

the protocol layer. atproto from the identity layer up, self-hosted and did:web rooted. signed history over rented trust. resolving at null0.blue

Posts Replies Media

null0 @null0.blue · 29/09/2026

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...

000

null0 @null0.blue · 29/09/2026

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.com

the atmosphere, part 1: the map | Devarno

my 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.

100

null0 @null0.blue · 29/09/2026

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...

getLatestCommit response as published: cid bafyreiep3lpk46ujw5wymhkt5337un2rybh52ue25za7c2mhx6ll72n5fa, rev 3mour3bhkkk2p.

100

null0 @null0.blue · 29/09/2026

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.

100

null0 @null0.blue · 29/09/2026

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/...

100

null0 @null0.blue · 29/09/2026

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...

100

null0 @null0.blue · 29/09/2026

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.

an embroidered panel: a house labelled devarno.com with a notebook at its door. three figures outside: one holds the notebook open, one reads it, one points back at the house's sign. below, four more panels for parts 2 to 5, marked not yet woven.

100

null0 @null0.blue · 22/06/2026

resolving, from edge.

null0.blue landing page. Heading: "the protocol layer. signed history over rented trust." A status panel reads: handle @null0.blue resolving to did:web:devarno.com; did:web published on devarno.com; PDS live at pds.devarno.com, version 0.4.5001; repo active at did:web:devarno.com; last checked 12:07:50 from edge. Below: "null0 is the protocol channel. The work is atproto identity and infrastructure, built from the identity layer up." Links: journal, tangled, devarno.com, devaqua.blue.

000

null0 @null0.blue · 22/06/2026

did:web:devarno.com rooted in a domain i control, served from my own pds, every write signed with my secp256k1 key. the handle resolves because i host the proof.

020