Select-only file index array in magnet url

[herrblitzkrieg]

Suggestion

A magnet extension that introduces the concept of an optional select-only file index array in the magnet URI, so that torrent clients can automatically select specific file(s) for download after the metadata has been downloaded. See extra info below for context.

Use case

No response

Extra info/examples/attachments

https://www.bittorrent.org/beps/bep_0053.html

[glassez]

https://www.bittorrent.org/beps/bep_0053.html

I wonder what is the advantage of this approach to make a multi-file torrent and produce a bunch of links pointing to specific files in it (assuming that they will be used separately), instead of making separate torrents? The client will still need to download the full metadata.

[herrblitzkrieg]

It makes sharing a magnet a lot easier, when the recipient (e.g. a seedbox, individual) can directly download just a part of an existing torrent. Also the recipient doesn't to have go through a long list of files and place check marks manually 🙂

[glassez]

Also the recipient doesn't to have go through a long list of files and place check marks manually 🙂

But it still has to go through a long list of magnets pointing to individual files of torrent and select needed ones manually, isn't it?

[herrblitzkrieg]

A magnet with a select-only file index array introduces inclusive ranges too (interpreted by dashes). This reduces the length of the magnet. The torrent client will automatically select-only part(s) of a torrent without any further user interaction. This is very handy with big multi-file torrents, also when they have lots of subdirectories.

[glassez]

The torrent client will automatically select-only part(s) of a torrent without any further user interaction.

But the user still has to find a magnet pointing to a suitable subset of files. By what principle and by whom are such links created? My question is still unanswered: if it is supposed to use some set of files, then why have many such sets in a single torrent, and not have separate torrents? If it is supposed to provide many different subsets of files from one torrent, then we will still have many such magnet links: why is choosing one of them better than choosing, say, a folder from a torrent?

[herrblitzkrieg]

But the user still has to find a magnet pointing to a suitable subset of files. By what principle and by whom are such links created?

Suppose I have made my selection of files (by check-marking files) and I click 'copy magnet', the file priorities will be embedded inside the copied magnet link (making use of a select-only file index array). So this concept applies to torrents that already exist and not to ones I am trying to create.

why have many such sets in a single torrent, and not have separate torrents?

Because some leachers may have interest only in certain files/subsets. The interest may differ from leacher to leacher, unlike the seeder. Some torrents may carry many files you actually don't want to share in your magnet link. Suppose I just wanna share parts of it, if I would create a new torrent from my selection of files, then I would have to seed it all myself alone where as the files are actually just duplicates from an existing torrent. Suppose I could share my file priorities embedded within the magnet, I won't have to seed to torrent myself, since it is part of an existing torrent, existing seeders are still valid . 👍

If it is supposed to provide mant subsets of files from one torrent, then we will still have many such magnet links: why is choosing one of them better than choosing, say, a folder from a torrent?

Why many magnet links? The same original (e.g. trackerless) magnet link just with a small addition at its end is enough already. Why choosing individuals files? Because a folder may contain even more folders or different files. Suppose you select a folder with a bunch of files it may look something like this: '4-38' . Selecting folder A and C may look something like this: '4-38,67-98' . Still pretty simple right? 🙂

[gothicserpent]

Duplicate of #7341

[herrblitzkrieg]

Yeah.......it's a duplicate.