You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Biggest load for DHT is the initial setup. Once it is connected to 100-200 links sending a request for peers for a torrent hash is minimal. I personally find 800-1200 is even faster. DHT is also used by other clients to find you faster not just you finding people to seed from. Without DHT lots of connection issues can happen. I can understand however that you might want less links to happen but DHT is more of an all or nothing technology.
I didnt fully understand all of what you said, which is fine.
I just wanted to add that my concern with DHT is mostly that of privacy (from what i understood of your reply, it was more so concerned about amount of connections and/or bandwidth etc.).
I didnt fully understand all of what you said, which is fine. I just wanted to add that my concern with DHT is mostly that of privacy (from what i understood of your reply, it was more so concerned about amount of connections and/or bandwidth etc.).
Don't know what he talking about either, I believe he trying to imply you cannot use DHT for specific torrents, but only globally, which is wrong.
He also seems to disregard the security hazards that come with using DHT, Sybil attacks anyone? qBittorrent should in my opinion have DHT and PeX disabled by default (as both are huge security hazards), but that is just me.
As for your suggestion, I agree we should have the option to enable it per torrent.
Suggestion
Currently, the UI lets me disable DHT globally, which is good.
But per torrent settings then only let me disable it, which it already is.
I would like to only enable DHT when I am having trouble finding peers, on a per torrent basis.
Use case
Keep DHT disabled for torrents that have peers that are easily found through the trackers.
Enable it for torrents that cant find any peers easily.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: