— @handle` from the article's own title instead of the tweet text (usually a bare `t.co` link). Article entries archived before this change are retitled on the next `archivr-server` start, but only while their title still equals the old auto-generated bare-link title; a renamed entry is left alone. Titles have no "edited" flag, so an entry you renamed back to exactly that old title is retitled too. CLI-only installs never run this pass — it runs at server startup only. X threads keep `Thread by @handle` at capture. **Generate title** in the entry rail (thread entries, user role and up) asks the selected Summary provider's cheap title model for a short topic and saves `Thread about — @handle` as the entry title (`POST /api/archives/:id/entries/:uid/thread-title`, body `{"provider": ""}`); rename it like any title. With ≥2 entries selected and at least one X thread, the bulk panel's **Generate titles** does the same for each selected thread (non-threads skipped; uses the Summary provider selected in the rail), two at a time, with progress and an `X updated, Y failed` summary; changing the selection stops it picking up further entries. Models are listed under [LLM providers](#llm-providers). ### YouTube playlists and channels Capturing a playlist or channel creates a **container entry** with each video archived as a child beneath it. Before downloading, the UI probes each video for available quality options — set quality per-video or apply one to the whole batch. Individual videos can be excluded with the remove button. **Sync mode:** when re-archiving a playlist or channel, enable sync mode in the capture dialog to skip videos that are already in the archive. Only new videos are downloaded; the existing container is reused. **Reordering:** if your role is allowed (by default Admin and Owner), expand a container on the main page and drag a video by its handle to change its position. On touch screens and phone-sized windows, where dragging isn't available, ↑/↓ buttons appear instead. Alt+↑/↓ on a selected row works everywhere. The order is saved to the archive. Videos added later by sync mode appear at the end. The Owner chooses which roles, including custom roles, may reorder under **Settings → Instance → Permissions**. ### Video quality and audio-only When capturing a yt-dlp-backed source through the web UI, a metadata probe runs first and populates the quality selector with heights actually available in that video: | `qualities` | `has_audio` | UI shows | |---|---|---| | `["1080p", "720p", …]` | `true` | Best / heights / Audio only | | `["1080p", …]` | `false` | Best / heights | | `[]` | `true` | Audio only (pre-selected) | | `[]` | `false` | "No media detected" | | probe fails (502) | — | picker hidden; capture still submittable | The `POST /api/archives/:id/captures` endpoint accepts an optional `quality` field: ```json { "locator": "https://www.youtube.com/watch?v=...", "quality": "720p" } { "locator": "https://www.youtube.com/watch?v=...", "quality": "audio" } ``` `"audio"` selects the most efficient native audio track without re-encoding (Opus/WebM preferred, then AAC/M4A). Omitting `quality` or passing `"best"` downloads at the highest available quality. ### YouTube subtitles YouTube video captures save subtitles next to the video by default: single videos, shorts, and every video archived from a YouTube playlist or channel, at any quality including audio-only. Subtitles apply to YouTube videos only — YouTube Music, Spotify, X, TikTok, and the other yt-dlp sources are downloaded without them. At most two tracks are saved, chosen from the metadata yt-dlp already fetches for the capture: - English, plus the video's original language when that isn't English. - Manual (uploader-provided) tracks are preferred. If the original language has no manual track, its auto-generated track is used; auto-generated English is used only when nothing else was found. - If the metadata probe fails, yt-dlp is asked for `en` and any `-orig` (original-language) track instead. Tracks are requested as VTT, with SRT accepted; nothing is converted, and other subtitle formats are dropped. Each file goes through the usual SHA3-256 dedup into `store/raw/` and is recorded as a `subtitle` artifact of the entry, along with its language, whether it was manual or auto-generated, and its format. Subtitle failures never fail a capture. Subtitles are requested in the same yt-dlp call as the media with `--ignore-errors`, so a missing track or a rate-limited caption request only logs a warning. If that call still fails, the media is retried once without subtitles. Subtitles are on unless you turn them off for a capture: - **Web UI:** the **Download subtitles** toggle in the capture dialog. - **API:** `"download_subtitles": false` in the `POST /api/archives/:id/captures` body. Omitting the field means `true`. - **CLI:** `archivr archive --no-subtitles `. Videos captured without subtitles can still be summarized; see [LLM providers](#llm-providers) and [Local transcription](#local-transcription-optional). #### Local transcription (optional) When a YouTube video has no subtitles at summary time, Archivr can transcribe its audio on the server. The order is fixed and transcription never runs if an earlier step yields usable subtitles: 1. archived subtitles; 2. subtitles fetched from the original video (subtitles only, no media); 3. local transcription with the engine chosen in the Summary panel; 4. the no-subtitles error (or a transcription-specific error if step 3 ran and failed). The feature is off until `ARCHIVR_TRANSCRIBE_ENGINES` lists at least one configured engine (env vars in [Local transcription env](#local-transcription)). Then the Summary panel shows a second selector on YouTube videos — **No local transcription** (default) or an enabled engine — remembered for the browser session. The API field is `"transcribe_engine": ""` in the summary POST body; an unknown or unconfigured engine is a 400. Enabled engines are listed by `GET /api/summary/transcription-engines`. | Engine (`kind`) | Languages | Runs on | Install | |---|---|---|---| | Whisper (`whisper`) | ~99 (`*.en` models English only) | CPU, Metal, CUDA/Vulkan | whisper.cpp `whisper-cli` + a ggml model (default backend), or a faster-whisper wrapper (`script` backend) | | NVIDIA Parakeet (`parakeet`) | v2 English; v3 25 European | NVIDIA GPU (NeMo), Apple silicon (parakeet-mlx), CPU (ONNX) | your own wrapper script; weights CC-BY-4.0 | | Fermion Phonon-2 (`phonon2`) | **English only** (hard-coded) | Apple silicon (MLX), x86-64/Arm CPU, CUDA | `pip install fermion-research` + platform runtime; weights CC-BY-4.0, CLI licence unknown | Setup examples: ```sh # whisper.cpp nix shell nixpkgs#whisper-cpp curl -LO https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-large-v3-turbo.bin export ARCHIVR_TRANSCRIBE_ENGINES=whisper ARCHIVR_WHISPER_MODEL=$PWD/ggml-large-v3-turbo.bin # Parakeet via parakeet-mlx (Apple silicon), wrapper from spec Appendix A.3 export ARCHIVR_TRANSCRIBE_ENGINES=parakeet ARCHIVR_PARAKEET_CLI=/opt/transcribe/parakeet.py # Phonon-2 (vendor package; Apple silicon shown) python3 -m venv /opt/transcribe && /opt/transcribe/bin/pip install fermion-research mlx mlx-audio mlx-lm soundfile scipy zstandard export ARCHIVR_TRANSCRIBE_ENGINES=phonon2 ARCHIVR_PHONON2_CLI=/opt/transcribe/bin/fermion ``` **Script contract** (Whisper `script` backend and Parakeet). Archivr runs `