Your devices

Nodes↑ Why · Alex loses a phone, and it opens nothing The lost phone is one key: revoking it touches nothing else.

Each node makes its own key, and the key never leaves it

A machine is revoked by its key; a copied key is two machines.

One node can be revoked without touching any other

A lost laptop must not mean re-enrolling everything.

Add a machine says which systems it runs on, and what each needs↑ Why · Alex reaches the laptop at home from a café Alex knows before installing whether the laptop at home is supported.

The first question is whether it runs on what you have; what isn't supported yet says so.

Joining↑ Why · Alex reaches the laptop at home from a café Alex adds the home laptop with one pasted line.

A new node joins only from a device already trusted

Joining is the one step that widens the account.

A pairing code lets in one key, before it expires

The code passes through a clipboard, a shell history or a camera.

A relay carrying a pairing learns nothing usable and can't change it

The relay is the part someone else may run, and pairing widens the account.

The install line checks what it downloads, and needs no root

It's pasted into a terminal, so it does only what it says: one file into your home, checked, then the pairing, then the node started and kept running, serving your home folder. Nothing is typed after it: a systemd user service where there is one, otherwise the background and cron.

Another browser of yours joins from a link the first one makes

A phone or a second laptop is a device of the account, not a guest, and needs nothing typed.

You choose how long a code works, and can type it

A link can't always be sent; a code read off one screen and typed into another can, and five minutes is enough to link a device.

A backup code written down adds a device with nothing else online

Lose every device and the account goes with them, unless some way in was put aside first.

The log↑ Why · Alex loses a phone, and it opens nothing The revocation reaches the machine with Alex's notes before it answers anyone.↑ Why · Sam lets an AI help, and decides what it sees The agent's grant to one folder until Friday is an entry in the log, revocable from any device.

Peers' keys come from the log, never from a handshake

A key learned on the wire is a key an attacker can offer.

The log merges in any order, and a revocation wins

Two devices add entries at once.

A grant gives one key rights on a scope, until it expires or is revoked

Every principal, a person, a machine or an agent, is a key holding grants.

The log crosses in every session, so a device added since is let in at once

A machine paired first must let in the phone added after it, with no server to ask.

Every session carries both sides' log heads, and the difference crosses in it

Whoever you talk to first brings you up to date, so no one place decides what you know.

A holder catches up before it answers

Revocation takes effect where the data is.

An account can set how stale a holder may be before it refuses calls

Availability against how fast a revocation bites; the account chooses, with a default.

Settings: yours, this device's, this moment's↑ Why · Jo's notes and code are on every device, and still files Jo's theme and workspaces follow Jo; the phone keeps its own zoom.

Settings today live in one browser and are lost with it, or sync whole, so a laptop's zoom lands on a phone.

Your devices

Nodes↑ Why · Alex loses a phone, and it opens nothing The lost phone is one key: revoking it touches nothing else.

Each node makes its own key, and the key never leaves it

One node can be revoked without touching any other

Add a machine says which systems it runs on, and what each needs↑ Why · Alex reaches the laptop at home from a café Alex knows before installing whether the laptop at home is supported.

Joining↑ Why · Alex reaches the laptop at home from a café Alex adds the home laptop with one pasted line.

A new node joins only from a device already trusted

A pairing code lets in one key, before it expires

A relay carrying a pairing learns nothing usable and can't change it

The install line checks what it downloads, and needs no root

Another browser of yours joins from a link the first one makes

You choose how long a code works, and can type it

A backup code written down adds a device with nothing else online

The log↑ Why · Alex loses a phone, and it opens nothing The revocation reaches the machine with Alex's notes before it answers anyone.↑ Why · Sam lets an AI help, and decides what it sees The agent's grant to one folder until Friday is an entry in the log, revocable from any device.

Peers' keys come from the log, never from a handshake

The log merges in any order, and a revocation wins

A grant gives one key rights on a scope, until it expires or is revoked

The log crosses in every session, so a device added since is let in at once

Every session carries both sides' log heads, and the difference crosses in it

A holder catches up before it answers

An account can set how stale a holder may be before it refuses calls

Settings: yours, this device's, this moment's↑ Why · Jo's notes and code are on every device, and still files Jo's theme and workspaces follow Jo; the phone keeps its own zoom.

Account state reaches every device

Device state stays on its device

A setting's tier is its schema's, not the writer's

Devices that edit apart merge

#Nodes↑ Why · Alex loses a phone, and it opens nothing The lost phone is one key: revoking it touches nothing else.

#Each node makes its own key, and the key never leaves itproof

#One node can be revoked without touching any otherproof

#Add a machine says which systems it runs on, and what each needsproof↑ Why · Alex reaches the laptop at home from a café Alex knows before installing whether the laptop at home is supported.

#Joining↑ Why · Alex reaches the laptop at home from a café Alex adds the home laptop with one pasted line.

#A new node joins only from a device already trustedproof

#A pairing code lets in one key, before it expiresproof

#A relay carrying a pairing learns nothing usable and can't change itproof

#The install line checks what it downloads, and needs no rootproof

#Another browser of yours joins from a link the first one makesproof

#You choose how long a code works, and can type itproof

#A backup code written down adds a device with nothing else onlineproof

#The log↑ Why · Alex loses a phone, and it opens nothing The revocation reaches the machine with Alex's notes before it answers anyone.↑ Why · Sam lets an AI help, and decides what it sees The agent's grant to one folder until Friday is an entry in the log, revocable from any device.

#Peers' keys come from the log, never from a handshakeproof

#The log merges in any order, and a revocation winsproof

#A grant gives one key rights on a scope, until it expires or is revokedproof

#The log crosses in every session, so a device added since is let in at onceproof

#Every session carries both sides' log heads, and the difference crosses in itproof

#A holder catches up before it answersproof

#An account can set how stale a holder may be before it refuses callsproof

#Settings: yours, this device's, this moment's↑ Why · Jo's notes and code are on every device, and still files Jo's theme and workspaces follow Jo; the phone keeps its own zoom.

#Account state reaches every deviceproof

#Device state stays on its deviceproof

#A setting's tier is its schema's, not the writer'sproof

#Devices that edit apart mergeproof

Nodes↑ Why · Alex loses a phone, and it opens nothing The lost phone is one key: revoking it touches nothing else.

Each node makes its own key, and the key never leaves it

One node can be revoked without touching any other

Add a machine says which systems it runs on, and what each needs↑ Why · Alex reaches the laptop at home from a café Alex knows before installing whether the laptop at home is supported.

Joining↑ Why · Alex reaches the laptop at home from a café Alex adds the home laptop with one pasted line.

A new node joins only from a device already trusted

A pairing code lets in one key, before it expires

A relay carrying a pairing learns nothing usable and can't change it

The install line checks what it downloads, and needs no root

Another browser of yours joins from a link the first one makes

You choose how long a code works, and can type it

A backup code written down adds a device with nothing else online

The log↑ Why · Alex loses a phone, and it opens nothing The revocation reaches the machine with Alex's notes before it answers anyone.↑ Why · Sam lets an AI help, and decides what it sees The agent's grant to one folder until Friday is an entry in the log, revocable from any device.

Peers' keys come from the log, never from a handshake

The log merges in any order, and a revocation wins

A grant gives one key rights on a scope, until it expires or is revoked

The log crosses in every session, so a device added since is let in at once

Every session carries both sides' log heads, and the difference crosses in it

A holder catches up before it answers

An account can set how stale a holder may be before it refuses calls

Settings: yours, this device's, this moment's↑ Why · Jo's notes and code are on every device, and still files Jo's theme and workspaces follow Jo; the phone keeps its own zoom.

Account state reaches every device

Device state stays on its device

A setting's tier is its schema's, not the writer's

Devices that edit apart merge