Preservation & Sharing
Understand direct and rendered capture evidence, local reader media, preserved copies, public snapshots, and asset-aware backups.
Arivu keeps private research evidence and deliberate public publishing as separate workflows. Direct capture remains useful without the isolated native capture runtime or a public link.
What Normal Capture Keeps
A link follows the ordinary capture pipeline. Safe direct extraction and isolated rendered capture can run together. Complete direct evidence becomes readable without waiting for the browser runtime, while stronger rendered evidence can improve a weak reader later. A failed browser run or challenge page cannot replace stronger evidence or the last good reader.
The selected reader shows capture-attempt history and retained source evidence with provenance and quality details when available. Reader pages also save scroll progress and serve captured article images from owner-scoped local storage, including images recovered by direct HTTP capture on core-only installations.
Source evidence is distinct from generated summaries and other derived material. A partial source may correctly have a short summary or none at all.
Complete Background Capture
Fresh installer runs on supported Linux hosts enable the isolated native capture runtime by default after presenting the plan. It renders pages headlessly in the background. It does not open a tab in your browser, read your browser profile, or receive your browser cookies. Choose --browser-capture=false for the core-only direct-capture path, or use arivu-installer reconfigure later to change the setting.
The reader’s preserved-copies panel can expose screenshots, PDFs, retained source responses, and self-contained offline HTML. Fresh installs enable screenshots and offline HTML by default. PDF is disabled by default and requires separate operator configuration because of its additional storage cost. Oversized offline pages remain downloadable without receiving an in-app preview.
The installer downloads and verifies the matching native runtime, checks it before activation, and manages upgrades, rollback, disabling, and removal. Operators do not need to install Docker, npm, Node, Chromium, or Monolith themselves. Existing installations retain their current choice during reconfiguration.
Preserved copies and reader media live beside the database in the private asset store and require an authenticated owner to read them. Capture remains bounded and is not a promise to reproduce every page or bypass a publisher’s access controls.
Create a Public Snapshot
From a bookmark’s Share disclosure, create an item-only secret link and copy its unrepeatable token when shown. Settings lists active public links and lets you revoke them. A snapshot can have an expiry.
The public copy contains selected public bookmark fields, sanitized reader content, and a snapshot of active reader media. It excludes owner details, private tags, notes, annotations, backlinks, graph connections, and Insights. Authenticated share APIs and local automation can deliberately replace membership, delete a share, or include selected screenshot or PDF artifacts. The bookmark disclosure itself does not select artifacts. Raw source responses and self-contained HTML artifacts are not publicly served.
Private Changes Do Not Rewrite the Copy
The public item is copied at publication time. Editing, recapturing, or deleting the private bookmark does not change or silently break that copy. An authenticated update can deliberately replace published membership under the same secret link. Revocation or expiry stops public access.
Each public share also has a bounded RSS endpoint for its newest published items. This public feed is different from private RSS and Atom subscriptions, which bring accepted entries into your capture pipeline.
Backup Implications
Installer-managed backups copy a consistent SQLite snapshot together with the adjacent asset store except staging and write a versioned size/hash manifest. Restore verifies a present manifest and treats the database and assets as a pair. Do not copy only a live SQLite file when retained artifacts matter.
Full JSON is the portable account-level export and restore format. It is not a replacement for an asset-aware host backup. See Import and Export and Self-Hosting Arivu.
Boundaries
Public snapshots are intentional, revocable publishing. They are not social networking, collaborative editing, a live workspace mirror, or an access-control substitute. Anyone with an active secret link can read its public snapshot, so publish only evidence you are prepared to disclose. Complete capture does not grant access to private, authenticated, or paywalled material that the capture runtime cannot legitimately retrieve.