ArnoldLayne

Oh, I'm not at all opposed to resolve it at hub configuration level. It would IMO be necessary to consider it anyway, whether DHT was activated by default or not in ApexD++. So maybe after all the fuzz created has been good in the sense that it's bringing hub admins' attention to DHT. Still, they're learning it the hard way and suffering a potential privacy threat meanwhile.

I already gave an example of that. Just imagine some files are shared that contains information that can be used to identify hub participants. A private hub is by definition a place where stuff is shared among a limited group of people. And DHT by definition makes the private material non-private.

Hi. My first post here, I'm sorry it has to be a negative one because in general I'm very grateful for all your efforts to keep ApexDC++ in shape. DHT is a security issue for private hubs, period. We can take for granted that many users just accepted the forced update and then went on to share files they thought still were confidential. DHT enabled by default is IMO quite similar to Microsoft's intentions to do the thinking that users should be doing. No offence, my critics is meant to be constructive, but it has to be said that respect for privacy is plain and simple "savoir être" in Internet. Cheers, AL