Development status

Development and publication work have resumed. Service APIs remain unavailable unless explicitly documented as live.

Local browser rescue

Keep locally what your browser has already received.

Triluna Document Rescue is being developed to preserve document bytes or pages already delivered to, or rendered in, the browser. It works within the viewer’s ordinary access boundary; it does not promise an original file when only a preview is available.

Local developer setup

The current source is for development, not browser installation.

  1. Open the Triluna repository on a local development machine.
  2. Open triluna-document-rescue/ and follow that subproject’s README for its source setup and checks.
  3. Do not load the core package as a browser extension. No Chrome or Safari browser package is provided by this local-only work.

Chrome and Safari on macOS remain intended targets. Safari has fewer extension capabilities for some capture methods. The exact support set must be stated and tested for each browser build before an installation guide or release is published.

Capture modes

Standard and Chrome Advanced have different permission boundaries.

Standard
The intended standard build uses browser capabilities that do not require Chrome’s debugger permission. It can preserve only material the selected build can lawfully observe; its actual coverage must be checked in that build.
Chrome Advanced
A Chrome Advanced build requires the debugger permission in its manifest. Chrome treats this as a high-access permission because it can attach debugging tools to a tab and inspect network activity. The user must choose Advanced and accept Chrome’s permission prompt; permission cannot be presented as optional inside that build. The implementation must attach only to the selected tab for an active capture and detach when it ends.

No advanced browser build is provided here. The permission description is a design boundary, not a claim that network capture is available.

Provenance before export

A saved preview is not silently relabelled as its source.

ORIGINAL
The complete source bytes were received and are saved byte-for-byte.
RECONSTRUCTED
A new file is assembled from page assets, images, HTML, or SVG that the viewer already exposed.
CAPTURED
Rendered pixels are preserved from a page or canvas. Text, metadata, vectors, attachments, and annotations may be absent.

The class must be shown before export and recorded in an optional sidecar manifest. A rescued artifact retains the source document’s available geometry and appearance as a user-source file. It is outside the TDS page-output contract and is not restyled to look like a Triluna publication.

Privacy and temporary data

Document bodies stay outside Triluna.

The browser-neutral core does not provide a Triluna upload path. A document body is not sent to Triluna. Any later browser build must keep working data in browser-local storage, provide an “Erase temporary rescue data” control, and remove abandoned partial captures. Those browser storage and cleanup controls are not implemented by the current core-only source.

Browser storage has finite quota; a large capture can stop when space runs out. Safari’s reduced extension capabilities may further limit which resources a build can see. Check the limits of the exact browser build before relying on a rescue.

Dropbox is an optional export provider, separate from capture and local download. Any upload would require a separate user authorization and export action. Browser compatibility and provider availability remain gated by platform testing; no Dropbox availability is promised here.