Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#3,285 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时
30 天内合并 PR
12

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

recloudstream/cloudstream 的其他 Issue

查看 recloudstream/cloudstream 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。