zebulon Posted October 16, 2005 Report Share Posted October 16, 2005 Can someone explain me why this option is necessary at this point ? If you're on a private tracker and use µTorrent to create the torrent, there's no risk anyway. What am I missing? Link to comment Share on other sites More sharing options...
Ultima Posted October 16, 2005 Report Share Posted October 16, 2005 Well that's true right now, when µTorrent doesn't support DHT yet, but it's all in preparation for the future. Plus, µTorrent isn't the only client that respects the private flag, so it isn't like the feature is going to go unused/unnoticed =] Link to comment Share on other sites More sharing options...
Firon Posted October 16, 2005 Report Share Posted October 16, 2005 Support to create torrents for the flag is so that torrents made with that client are private. The torrent must be explicitly made with the private flag, because it changes the infohash. A private tracker can't set this flag after its creation. Other clients will use the torrent, and if they are DHT-enabled and respect the private flag, DHT will be disabled for them, as it should be on a private tracker. Link to comment Share on other sites More sharing options...
MrCoke Posted October 16, 2005 Report Share Posted October 16, 2005 thank you for adding this feature!! it helps to reasure if i'm making a private torrent. its not just the fact that this client is awesome, it the fact that they know what people want, adapt and make changes by the next build... its a great job guys:D Link to comment Share on other sites More sharing options...
zebulon Posted October 16, 2005 Author Report Share Posted October 16, 2005 @ Firon: that's right, I didn't think about that. Enforcing other clients to respect private torrents is fine. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.