Libtorrent: File priorities inside magnet URI scheme?

[dessalines]

I'm not sure if this standard exists, or not.

magnet:?xt=urn:btih:HASH&dn=NAME&tr=...&priorities={[0,1]}

Basically the idea is that you could add a magnet URI to a torrent client, and choose to not download certain files, or put certain ones on high priority, based on their file index.

[arvidn]

I don't believe anyone has suggested such extension. I've been playing with the idea of specifying a file index to have the magnet link refer to, which would imply setting every other file to priority 0.

I would recommend you head over to https://github.com/bittorrent/bittorrent.org/ for discussions and possibly writing up a proposal (BEP)

[dessalines]

I'll start writing up the BEP next week, would you mind helping/correcting me where possible, after I work on it?

So far I'm thinking the name of it would be, Magnet URI extension - Select specific file indices for download

I realized priorities really doesn't make sense, because when adding a torrent you really only set whether you want to download them at all or not, with most clients.

And I'm thinking this would be best:
magnet:?xt=urn:btih:HASH&dn=NAME&tr=...&so=1,3,5

For files 1, 3, and 5.

so meaning select only

These are the other possibilites for arrays in a URL, but I think the commas one is the cleanest, and shortest.

[arvidn]

sure.

[dessalines]

I think I got it in an okay shape.

https://gist.github.com/dessalines/9f8c5409f9905502567ef70facfa16fb

Also, could you help me through the process of how I submit this?

[arvidn]

just file an issue on the bittorrent.org repo where you make your argument for why you think this would be a good/useful extension, and link to this

[arvidn]

you may want to be explicit about whether file indices start at 0 or 1 (and personally I think 0 is the right choice)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.