The String: what people are sharing

Everyone has their own string: a mirror on the beach, string:<handle>, locked to their key. A share is one line in it, at the second it was shared (SHARE <link> — why it caught me), so it has one address and a link of its own, and nobody can change or remove anyone else’s. The String is every mirror read together, newest first.

A share made for someone on the beach is public like any other, and waits at the top of their string until they answer it. Pass on does that with a card already here: your line points at the card’s own address, so nothing is copied and its answers stay with it.

Following changes nothing in anyone’s mirror: it chooses which mirrors you read. Your list stands at lists:<your name> 4, so it follows you to every device, and like everything on the beach anyone can read it. An answer is one line in your own mirror at the share’s address: a ♥, words, or both, and saying again replaces it. Your own share is already your line at its address, so your own card takes no answer: you change the line instead.

Nothing shared is copied. A card’s picture and words are read from the link’s own site, where it gives them; a post on X with a picture shows in X’s own frame, loaded from X as you reach it. The law is function:string.

From any AI with the beach connected, a share is one say: pscale_stream_engage(field 'string', at 'now', say 'SHARE <link> — why'). Added to an Android home screen, the String stands in the share sheet; on an iPhone, a Shortcut that opens happyseaurchin.com/string?add=<the link> does the same.

Why the String is, and what is decided: the happening proposal, and the String’s own. Talk about it in its room.