share · replay · re-derive

You did not trust my screenshot. You re-derived my desktop.

A shared deos desktop is not a picture and not a state blob. It is a tape: a pinned genesis instant plus the sequence of messages a session sent, small enough to live in a URL fragment. Your viewer boots a fresh world at that instant and re-executes the tape through the same verified executor the sharer used — then compares its re-derived canonical ledger root against the root the link claims. The headline of a shared desktop is an equality, not an image.

This link's tape

Paste a share fragment below (or arrive here with one after # in the URL — it is read automatically). What you see here is a display-only preview decoded in this page's JS for legibility; the authority is the replay your viewer server performs. This page never replays anything itself and holds no world.

no tape yet — paste a fragment, or open a share link ending in #deos1!…

The grammar (one line, forever)

deos1!ts=<unix>[!tab=<surface>][!root=<64 hex>][!act=<cell hex prefix>:<verb>]…

What the viewer server does with it

The whole route is stateless and read-only: a stranger's link buys a bounded replay (32 acts max) against a throwaway world. It cannot drive the live cockpit, and there are no live turns from strangers — sharing a desktop hands over a derivation, not a capability.

Honest scope. Today the replaying server is the local --serve-ie6 cockpit server (bound to 127.0.0.1), so “shareable” means: anyone who runs deos can paste your link into their own viewer and re-derive your desktop — the link format is server-independent and carries no secrets. A hosted read-only viewer and the wasm cockpit adopting the same fragment are the natural next welds; the codec (starbridge_v2::share_link) is pure and round-trip-tested precisely so both glasses can speak it unchanged.