Skip to content
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

BEP draft - Magnet URI extension - Select specific file indices for download. #64

Merged
merged 4 commits into from
Jun 6, 2017

Conversation

dessalines
Copy link
Contributor

@dessalines dessalines commented May 31, 2017

Issue #63

@ssiloti
Copy link
Contributor

ssiloti commented Jun 1, 2017

I still think the Rationale needs to have a justification for why this enhancement is necessary to improve the UX when selecting specific files to download. Currently the only concrete issue that's raised, having to manually start/pause the torrent to get the metadata, could be fixed without this.

@the8472
Copy link
Contributor

the8472 commented Jun 2, 2017

In my experience any torrent not near death can download the metadata almost and then present the file selection UI almost instantaneously.

@dessalines
Copy link
Contributor Author

I'll change the rationale to the deep-link one shortly, as that is my main use case for the site I'm building anyway.

@gubatron
Copy link
Contributor

gubatron commented Jun 2, 2017

👍 👍
We could use this on FrostWire's individual file search results.

FrostWire presents search results both as .torrents and when the metadata is available we're able to show matching search results by looking at the file list, we present these results as individual audio, video, apps, docs, etc. search results.

screen shot 2017-06-02 at 12 03 25 pm

All .torrent search results now have a "Copy Magnet URI" action available, this would improve sharing a single file from a torrent from FrostWire to FrostWire or other clients.

So, that'd be another use-case out of the realm of websites.

@ssiloti
Copy link
Contributor

ssiloti commented Jun 2, 2017

Please update the PR to make this BEP 53.

@kovalensky
Copy link

kovalensky commented Jun 14, 2023

From arvidn/libtorrent#7439 could we be more clear in BEP in the context of processing padding files?

Meta files compatible with BitTorrent version 2 (especially backwards compatible hybrid torrents) containing indices do not work with BEP 0053.

File indices for padding files could be discarded of course, but it would be nice to include this behavior in the BEP to avoid confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants