sharing
Send a set to someone
open a node's menu and choose share
type their @user-id and press Share — the node now carries a share offer
the dialog also hands you a preview link to send: it points at /share/…
they open it, tick the rows they want, and press Accept selected or Accept all
Accepting is forking
accepting builds them their own instance of the set, with you still as its creator
the offer is consumed once per person, so several people can each accept independently
what they accepted lands in their expand and stays in sync with the shared elements
Someone else's sets are read-only
a set whose creator is not you shows a hollow bullet
you cannot type into it, and the node menu hides every action that would write
Public to every lisct user
,anymakes a set readable by anyone signed in to lisct — unlike a doc site, this one is not open to the anonymous web
at the same /share/… address readers get Collect instead of Accept
collecting copies the set to them and leaves your original untouched, as many times as they like
One limitation to know
editing a shared node changes its identity, which invalidates a preview link you already sent
reopen the share menu and copy the link again after you edit