[Feature]: Desktop app: offline downloads
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
- Issue-Typ
- Feature
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- backend-api-design, desktop
Rechercherichtung
Read the epic #80 first, then inspect #81 for the cache/data directory and #84, #86, and #91 for media downloads and playback; start only after web parity is reached, as the issue specifies. The music path references /api/music/tracks/{id}/file, and the video path references /api/media/{id}/file?download=1. Done means downloaded episodes and albums play without a network connection with subtitles, fonts, artwork, and lyrics, and offline progress appears on the web after reconnecting.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a planning session with @PhrolovaMoe. Part of #80, builds on #84, #86 and #91. Start after web parity is reached (all other sub-issues except #95 done). Read the epic first.
Area
Desktop app
Problem
On a laptop away from home (train, plane, bad hotel Wi-Fi), the app is useless without a connection to the server.
Proposed solution
Downloads
- Download episodes, films, seasons, albums and playlists to local storage: video through
/api/media/{id}/file?download=1(#84), music through/api/music/tracks/{id}/file. Downloads are resumable (Range) and run in the background with a queue, progress and pause/cancel. - Download alongside each item what offline playback needs:
- subtitles (the server's ASS for each text track) and fonts;
- artwork, metadata, chapters and intro/credits markers;
- lyrics for music.
- Optional "download a smaller version" (a server transcode at a chosen height), if the server can produce a downloadable transcode. If it can't, file a follow-up server issue instead of adding it here.
- Per server, in the cache/data directory from #81. Storage use is shown and managed in Settings → Desktop.
Offline mode
- When the server can't be reached, the app shows the downloaded items (a "Downloads" view) instead of erroring, and plays them from disk with the same player (#86/#87/#91).
- Progress, watched state, plays and scrobbles are queued and sent when the server is reachable again (oldest first; on conflict the newest position wins, as the server already decides for multiple devices).
- Music gets the Android plan's behaviour (#47): an LRU cache of recently played tracks, pinned albums/playlists, and prefetching the next 3 queued tracks.
Done when
Downloaded episodes and albums play with the network off: subtitles, fonts, artwork and lyrics included. Progress made offline shows up on web after reconnecting.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 4
- Forks
- 1
- Ø Merge
- 4 Std. 49 Min.
- Gemergte PRs (30 T.)
- 5
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Kein Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus tinystream-dev/tinystream
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
tinystream-dev/tinystream#132 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
tinystream-dev/tinystream#131 ·
-
bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
tinystream-dev/tinystream#129 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
tinystream-dev/tinystream#128 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
tinystream-dev/tinystream#124 ·
Alle Issues in tinystream-dev/tinystream
Ähnliche Issues
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOffen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 86/100
sandbox-quantum/switch#2163 ·
Maintainer antworten meist innerhalb von 1 Tag
-
automated issue report
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
area/dashboard kind/bug QA/dev-automation
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 75/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug pydanty:is-working
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
pydantic/pydantic-ai#13939 ·
Maintainer antworten meist innerhalb von 1 Tag
-
self-host
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
funmusicplace/mirlo#2625 ·
Maintainer antworten meist innerhalb von 1 Tag