Publish to the web

Publishing creates a read-only snapshot for people who may not have Lar. It is distinct from private sharing: readers receive no editing access and later Object changes are not live until you update the publication.

Create a publication

1. Open the Object and choose Share.
2. Select Publish to web.
3. Choose the body, properties, and attachments that are safe to include.
4. Optionally request a custom link when the configured server supports custom slugs.
5. Choose Publish.
6. Copy the resulting URL.

The selection is a disclosure boundary. Properties or attachments you leave out are not placed into the published snapshot.

How the link protects content

Lar encrypts the snapshot before upload. The server stores ciphertext under an opaque identifier or custom slug. The decryption key lives in the URL fragment—the part after #—which browsers do not send in the normal HTTP request. The publication page fetches ciphertext and decrypts it in the reader’s browser.

Caution

Anyone with the complete URL can read and copy the selected snapshot. Treat the URL like a secret. Link-fragment encryption prevents the publication server from reading content; it does not prevent an authorized reader from redistributing it.

Update a publication

Open Share → Publish to web, review the selection again, and choose the update/republish action. Updating replaces the published snapshot; it does not turn the page into live collaboration.

Unpublish

Choose Unpublish and confirm. This prevents future retrieval from the publication endpoint. It cannot retract content already loaded, cached, downloaded, or copied by a reader.

Manage publications

Open Shared → Published by me to revisit locally recorded publications. Custom-slug availability is decided by the configured server, so the field can disappear after a server rejects that capability.

For ongoing account-based access, use Sharing an Object instead.