-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Create .torrent and/or magnet hashes mounts them #86
Comments
Since reporting this issue (earlier today) I've been playing with the code to hack in the above. Would it be possible to refactor this to be ready for multiple torrents on a technical level? |
Hi,
The title is a bit tricky but describing it probably helps in understanding what i'm asking.
What if you could add torrent file or magnet hash in a BTFS mount point where BTFS would handle the "mounting" of these new files automatically?
Here's an example of how such a mount action would look like:
mkdir mnt btfs mnt cd mnt
Note that the
btfs mnt
in this example gets no torrent or magnet.Let's assume the torrent / magnet content is:
Inside this
mnt
folder one can then add torrent files or magnet hashes like so:Or with a magnet hash:
The idea here is that
BTFS
internally takes care of mounting torrent files and magnet hashes.What you'd end up with is a filesystem in which you can drop torrent files and magnet hashes which then automatically become browsable as soon as
BTFS
has downloaded the torrent metadata to present the content hierarchy.Removing the torrent or magnet hash should remove the "mounted" data too.
The user would only be able to create and remove torrent files or magnet hashes in the root level of the
BTFS
mount.I did have a quick look at the code. Currently it seems focused on handing a torrent as it got it as mount argument. So implementing this proposed feature probably is a quite big refactor. I do think it's worth it though as having completely transparent torrent mounting would be super nice to have! As far as i'm aware, a feature like this on a filesystem level doesn't exist. Torrent clients do have this feature somewhat, you can open a torrent/magnet and see what's inside. But that's by no means a filesystem like interaction.
As a cherry on top, this can be neatly integrated into file managers like KDE's Dolphin. There for example it would be possible to add the option to open a torrent. Internally that would add the torrent to the mount point that can handle it and potentially a symlink would be created from that torrent to the user's home folder making it completely transparent from a user point of view.
The text was updated successfully, but these errors were encountered: