Uploads and sharing¶
On private instances, Settings > Uploads lists files you uploaded and message links you shared. Availability, size limits, and expiration are controlled by the administrator.
Relay can remove supported image metadata in the client before upload and sanitizes supported images again on the server. Review the result before sharing sensitive media.
Automatic pastebinning¶
On private instances, sending five or more lines creates a paste link instead
of sending the full text to IRC. In Settings > Uploads > Pastes, change the
threshold or set it to 0 to disable, and open, copy, or delete existing pastes.
Typed and pasted text both count; blank lines and code fences count, but visual
wrapping does not.
Anyone with the link can read a paste. Pastes preserve whitespace and IRC formatting, highlight language-labeled code fences, and offer raw text access. On current master, Copy all copies the original source; if clipboard access is blocked, open Raw text and copy manually. They support up to 256 KiB and follow the server's upload expiration policy even when file uploads are disabled. Encrypted conversations, slash commands, and local Partyline messages bypass paste creation. Failed creation keeps the draft; after a timeout, check the Pastes tab before retrying.
Shared messages¶
On current master, after 0.11.2, share a conversation excerpt by opening a message's ⋯ menu and choosing Select messages. Select up to 20 messages from that conversation, choose Share selected, review the preview, then choose Create public link. Nothing is published before that confirmation. Anyone with the link can read the snapshot, including selected decrypted text; inspect it before publishing. Manage and revoke collections under Settings > Uploads > Shared messages. If creation times out, check that list before retrying. These are shared snapshots, not verified IRC transcripts, and revocation cannot erase downloaded copies.
Use Copy message link on a message to create a read-only share. Sharing requires a private authenticated account; it saves a snapshot and does not require message logging or file uploads to be enabled. Anyone with the resulting link can read the shared snapshot; review the content before distributing it. The Uploads page shows each share's creation and expiration time and lets you copy or delete it. Deletion removes the server copy and cannot be undone. At the audited commit, Relay's service worker can still show a previously cached share after the server returns 404; deletion does not erase cached or downloaded copies.
Short links and DCC files¶
When enabled, Short Links lists your redirects and lets you sort, open, or delete them. Experimental DCC transfers require approval before download; received files are private to your account and appear with their expiration time.
Upload and expiration¶
When uploads are enabled, use the composer's file control, paste a file or drop one into chat, then review the resulting link before sending. The server defaults to a 10,240 KiB maximum (10 MiB) and 24-hour expiration, but uploads themselves default to disabled. The administrator may choose a different limit or disable expiration. The proxy can impose a lower request limit.
Shared messages use the upload expiration setting when created. Expiration or deletion makes a link unavailable; it cannot recall copies already downloaded by recipients. Short links have their own expiration policy. Keep important originals outside Relay instead of treating temporary uploads as a backup. DCC transfers additionally require administrator resource budgets and your approval of the incoming offer.