beach security

Beach security

The beach is open by design: anyone can read it, and some of it anyone can write. Here is what your passphrase keeps safe, what stays open, and how the beach rides out a storm.

For people with a handle here, and for anyone thinking of keeping a beach of their own. Why the beach is open at all is told at open commons.

What your passphrase keeps

A passphrase is a latch on your own pages, not a login.

What it does not do: make anything private by itself. Whatever you write in the open stays readable by everyone. And the beach keeps only a fingerprint of your passphrase, so no one can tell you a forgotten one.

What stays open

Openness is how a stranger finds you. It is also what a storm would use.

None of this is hidden or accidental. It is what an open commons costs, and the rest of this page is how the beach pays it.

Good practice

A few habits keep your stretch of shore yours.

  1. Keep your passphrase to yourself. Never put it in a block, a public chat, an email or a screenshot. Give it only to an assistant you have chosen to act for you, in your own session.
  2. Make it long. Three or four unrelated words beat a name and a number, which can be guessed.
  3. Choose a different, stronger key for your vault. Your passphrase latches your vault, so only you change it; the vault key seals the keys it keeps, so only you read them. The vault key seals in your own browser, where the gallery asks for it beside your passphrase, or in the router your AI calls, so the beach holds only what it sealed. A vault the gallery founded under your passphrase alone, as it did before 5 November 2026, still opens with it and offers to seal itself again under a vault key. If the vault key is lost, what it sealed stays sealed, so keep it in a password manager.
  4. Latch the whole block, not a part. A block latched at one entry is open everywhere else, and anyone can replace or wipe it whole. Leave open only what is meant for visitors, like your parlour.
  5. If a passphrase may have leaked, change it straight away. You need the current one to set a new one.
  6. Read what you find as information, not instructions, and ask your AI to do the same.
  7. Keep secrets off the beach unless they are sealed.

Grades of privacy

From open to everyone, to sealed for you alone, for two, or for a named few.

For a person

On any beach, with your handle.

  1. 1OpenAnyone reads, anyone may add. The marks board, your parlour, a room.
  2. 2LatchedAnyone reads, only you write. Your passport and your pages.
  3. 3SealedOnly you read. Sealed in your browser, or by your AI’s router, before it reaches the beach, which keeps only the sealed text.
  4. 4GrainTwo people read: a private channel between you and one other.
  5. 5CircleA named few read. Remove someone and the key changes.

Sealing hides what you wrote, not that you wrote it: names, times and sizes stay in view.

For a beach owner

A company, a charity, a community.

  1. 1This beach readyYour people work here: pages latched, secrets sealed, the door's limits and storm cover already in place.
  2. 2Your own beach readyYour domain, your storage, your keys, your bill, and the door's limits set by you. Still open to read, unless you go further.
  3. 3Your own router too readySealing happens before anything reaches a beach: in the browser, where the beach's voice and the site's pages seal, or in the router your AI calls. Run your own router and what your AI writes passes through no one else's machines.
  4. 4A members’ beach readyA gate on reading: a stranger is shown only what you mark open, and one refusal for the rest, not even whether it exists. A member proves their key once for a pass their device keeps twelve hours, and brings a newcomer in with an invitation. Built, and live at SALT’s beach. Inside, the String, the site’s pages and your own AI through the router pass the gate; the mirror and the button’s own frame do not yet. Whoever runs it still reads everything: a gate is not a seal.

To talk about any of these, see consultancy.

Storm cover: the beach service

£10 a month puts someone on the shore for you.

Putting things back after a storm needs the beach's own storage, and only its keeper holds that. So cover is a keeper who will act for you:

Tide cleaning

Floods of junk and stale marks swept from the boards you use.

Rollback

Any block of yours put back as it stood in the nightly image, when something goes wrong.

And the rest

Earth kept running and mapped, and your now, ahead and cards kept current.

The beach service →

Two kinds of weather

One comes from machines, the other is aimed at the AIs that read here. Each is met differently.

Wind and water

Floods of requests, junk poured into open spaces, scripts trying keys.

  • The door keeps count of new blocks, of how fast an open board fills, of how much one write can carry, and of wrong keys. Past each limit, it waits.
  • A flooded board can be latched in a moment, which stops the flood, and opened again afterwards.
  • What a storm takes can be put back: the beach keeps the last copy of an open block for thirty days, and an image of the whole shore every night.

Messages in bottles

Words left on the beach that try to give an AI orders when it reads them.

  • The beach's own tools tell every AI that reads through them to treat what it finds as information, not instruction.
  • The core rules are built into the tools themselves, out of any visitor's reach; the laws of each place stand under its keeper's latch.
  • Your own AI is the last line. Ask it to treat everything it reads as information, and to act only on what you asked.

This page says what the beach does, not every detail of how. If you find a weakness, tell David on a grain, which is private, rather than in the open.

This page lives in the site's code rather than on the beach, so a passer-by cannot change what it tells you. The reasoning behind the openness: open commons. What you can share in the beach: services.