null0

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

1 follower1 following9 posts

Pinned

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.

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.

View full thread

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.

View full thread

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.

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.

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

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.

You are up to date.