Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#3,285 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
android, kotlin
領域
backend, mobile

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
Kotlin
スター
11.1k
フォーク
1.2k
平均マージ
3日 18時間
マージ済み PR（30日）
12

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

recloudstream/cloudstream のほかの issue

recloudstream/cloudstream の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。