-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
A macOS location for app-managed persistent data. Under App Sandbox, the exact path can live inside the application's container.
A normalized downloadable Telegram media/file record containing identity, filename provenance, category, known size, sent date, and eligibility.
The combination of Telegram chat ID, message ID, and file ID used to distinguish attachments independently from display names.
A history scan limited to the latest 25, 50, 100, 250, or 500 distinct messages.
A state where a planned destination already exists or two selected files plan the same destination path.
An explicit temporary override of the local already-downloaded guard. It does not override filesystem conflict safety.
A neutral deterministic fallback used only when Telegram provides no usable original or file-representation filename.
The macOS credential store used for the Telegram API ID and API hash.
The selected history scope. It is part of the attachment-cache key and is saved per chat.
The filename supplied by Telegram's media representation. It is preferred over music metadata, captions, or generated names.
The required preparation step that deduplicates Telegram file IDs, calculates known size, checks destination capacity, and discovers filename conflicts.
An explicit conflict action that creates a new destination name using a visible copy suffix.
A persistent macOS token that lets the sandbox reopen a folder previously selected by the user.
A partial or complete local attachment index for one chat ID and message range.
Telegram Database Library, the official Telegram client library used for authorization, chats, history, updates, and file transfers.
Telegram's file identifier used for transfer and the local already-downloaded guard. It is not a content hash.
Swift isolation used for observable interface state and user intents.
A Swift concurrency construct used to serialize access to mutable shared state such as TDLib requests, repositories, persistence, downloads, and destination access.
Unspool is an independent project and is not affiliated with Telegram. Repository · Privacy · Security · MIT License
- Getting Started
- Detailed Telegram Setup
- Feature Overview
- Chats and History
- Attachments and Filenames
- Search and Selection
- Download Workflow
- Conflicts and Recovery
- Download History
- Settings
- Accessibility
- Troubleshooting
- Detailed Troubleshooting and FAQ
- Privacy and Security
- Detailed Security Model
- TDLib Integration
- Persistence
- Concurrency and Errors
- Glossary