Joining pairs this exe with another one (say, your laptop's). From then on the two share what their apps save, their Workspace files and their Newsfeed: a note written on one is on the other when you sit down at it.
Joined nodes sync continuously, both ways:
VMs, the configuration and the disks of the Mac OS 9 and Mac OS X apps (Intel included) are not synced: each stays on its own node. Joining gives the other node the sync and nothing more: not your VMs, your configuration or a shell.
The two nodes must be able to reach each other, as they can on one tailnet.
:port after it if its desktop is not on 7777) and the code, and press Join.Joined nodes lists each node with a lamp that is green while it answers, its address and how many milliseconds away it is. Leave, pressed twice, stops the sync with that node, which is told and drops this one too. Join a third node to either of two joined ones and all three sync with one another.
Lists the apps keep item by item, such as to-dos and notes, are merged item by item, so what either node added or changed survives. For any other file one copy wins and the other is saved in ~/.exe/sync-conflicts, and the Newsfeed says so.
The Newsfeed (Windows → Newsfeed, or its icon on the desktop) is the shared timeline of the mesh: VMs created and deleted, nodes joining, sync conflicts. Each item names the node it came from. Agents can post to it with POST /v1/newsfeed, so finished work or problems show up on every desk.