Track tasks and feature requests
Join 40 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesclient.add(infoHash [in hex]) doesn't appear to work. #902
Comments
This comment has been minimized.
This comment has been minimized.
|
Have you set the torrent trackers ? |
This comment has been minimized.
This comment has been minimized.
|
nope. if |
This comment has been minimized.
This comment has been minimized.
|
Check out this comment: #672 (comment) |
This comment has been minimized.
This comment has been minimized.
|
Oh interesting, thanks! :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@feross I think it is confusing for sure, having the same behavior, or possibly giving a warning when omitting any trackers, would clear it up. I get why not having default trackers is a good idea, I just think it would be good to be consistent. |
This comment has been minimized.
This comment has been minimized.
|
@mikeal Did you specify at least 1 custom tracker? If not, then this is a bug, as it should add the default ones. |
This comment has been minimized.
This comment has been minimized.
|
@DiegoRBaquero I think it's a bug because it doesn't add the default ones when a tracker is not specified. It works great with magnetURI though. EDIT: |
latest as of today :)
6.x cause I'm a responsible developer :P
Chrome 53
The docs say
client.add()will work with an infoHash hex but it's not working for me. I literally seed a file in one tab and try to get it in another and it can't load the metadata. If i swap that out for a magnet url it works great.