Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request] Media Servers, File Transfer Protocols and/or Cloud Drives Support

Aperta
  • Qualcosa non va?
#3,285 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
backend, mobile

Direzione di ricerca

Start by reading the extension API and the app’s ExoPlayer integration to see where external media sources could fit. The request spans media servers, several network protocols, cloud drives, authentication, subtitles, and watch progress, and leaves the core versus extension design undecided. Done would require maintainers to choose a scoped approach and define supported sources and expected behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Describe your suggested feature

Right now CloudStream is my main app for streaming via extensions, but I still have to switch to other apps (like Kodi, Nova, or VidHub) whenever I want to watch stuff from my WebDAV, home server, cloud drives etc.

It would be awesome if we could get support for self-hosted media servers, basic network file protocols, and cloud storage directly inside CloudStream—mainly so we can use CloudStream's UI and built-in subtitle providers (OpenSubtitles, Subdl, etc.) for our own media too.

Here is roughly what I had in mind, broken down by what actually makes sense to implement:

1. Media Servers (Jellyfin, Emby, Plex)

Since these already have their own APIs with posters, episode metadata, and watch history, they would fit really well into CloudStream's existing homepage and catalog layout.

  • Being able to add a server URL + login/API key.
  • Direct play support (passing the stream URL + auth headers to ExoPlayer) and basic watch progress sync.
2. File Transfer & Network Protocols (WebDAV, SMB, FTP/SFTP, NFS)

For watching raw video files stored on a local NAS or a remote seedbox:

  • WebDAV and SMB (v2/v3) are the most important ones here.
  • FTP / SFTP would be great for seedboxes (and maybe NFS, though I know NFS can be annoying to implement on non-rooted Android).
  • Since raw folders don't have metadata like Jellyfin, a simple folder/file browser (or optional filename matching with TMDB/AniList) and automatically loading external .srt / .ass subtitles sitting in the same folder would be more than enough.
  • ExoPlayer would just need proper byte-range seeking (DataSource) so we can scrub through large MKV files without buffering the whole file.
3. Cloud Drives (GDrive, OneDrive, Dropbox, Box, pCloud, YandexDisk, MEGA, Aliyun, 115, 123 Cloud, Baidu NetDisk, GuangYaPan, etc.)

Obviously, adding native SDKs and OAuth logins for 10+ different cloud services—especially tricky ones like MEGA (client-side decryption) or Chinese drives like Aliyun, 115, 123Pan, and Baidu—directly into the main app would bloat the APK and be a nightmare to maintain.

Instead, I think there are two realistic ways to handle cloud drives:

  1. Solid WebDAV support (with HTTP 302 redirects & custom headers): A lot of people already use tools like Alist or Rclone to mount all of the cloud drives mentioned above as a single WebDAV server. If CloudStream's WebDAV client properly handles 302 redirects and custom User-Agents, all of those cloud drives will automatically work out of the box with zero extra maintenance for the devs.
  2. Extension API support: For users who just want direct Google Drive, OneDrive, or Dropbox access without setting up Rclone/Alist, maybe the core app could expose the basic auth/folder hooks so plugin devs can maintain individual cloud providers as extensions.

I'm not sure how much of this makes more sense to put in the core app (like the ExoPlayer DataSource implementations for SMB/WebDAV) versus offloading to the extension system, so I wanted to open this issue and see what the maintainers think. Thanks for all the work on the app!

Other details

No response

Acknowledgements
  • My suggestion is NOT about adding a new provider
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
Lingua principale
Kotlin
Stelle
11.1k
Fork
1.2k
Merge medio
3g 18h
PR unite (30g)
12

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di recloudstream/cloudstream

Tutte le issue di recloudstream/cloudstream

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.