recloudstream / recloudstream/cloudstream
Support for External .torrent Files
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 10.7k
- Forks
- 1.1k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 15
Description
Describe your suggested feature
Is your feature request related to a problem? Please describe.
Currently, there is no way to stream content by opening external .torrent files directly through the app.
Describe the solution you'd like
Add full playback support for external .torrent files.
MIME/File Association: Allow the app to be registered in system file-open prompts for .torrent files.
Direct Input: Provide an in-app option to paste a magnet link or select a local .torrent file from storage.
Since the app already supports torrent streaming via the internal catalog, could you please add file association support for external sources?
This would allow users to utilize the app's playback engine for torrents outside the built-in catalog.
Could you please add support for handling external .torrent files directly within the player?
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing torrent streaming path in the app and the player’s handling of external inputs. Check how Android file associations are currently declared, then trace the internal catalog flow to determine what must support magnet links and local .torrent files. Done means an external .torrent file can open in the app and its content can be played.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100