LjL
LjL
@jf99 for most commonly-used types of DHTs to work efficiently, you need a logarithmic number of connected peers (logarithmic to the total amount of users, that is). I was told...
Whatever, really. I've explained things clearly, and that direct connections can and should be made through UDP and not TCP, and I'm not discussing with someone who calls what I...
- I think realistically, **two** TCP connections rather than one would be ideal, because a TCP relay can always go offline (it can be any peer after all), and there...
@aaannndddyyy I agree that very immediate offline-status detection is not a necessity, but I think 10 minutes is _way_ overkill. And don't forget the other part, i.e. that it can...
@Renha This mode where people don't partake in the Tox DHT already exists, it's called TCP-only mode, and any client can enable it. People can already elect to use it,...
@gianni76 with UDP mode, you communicate directly with your friends, but you also take part in the DHT, which translates Tox IDs into IP addresses (people must know what their...
@gianni76 as to "Zero reason to user relays": perhaps you've never been under a hard, symmetric, ISP-enforced NAT. I cannot communicate with other similarly NAT'd clients without the help of...
@gianni76 you are misguided and you aren't listening, I am not "totally wrong". If encryption somehow weren't enough to stop "data tampering", then that could happen at any router along...
@mrkiko There is no such thing as "UDP relaying" in Tox, only TCP relaying (unless the onion routing counts perhaps, but that is only used for DHT queries). And yes,...
Connected DHT nodes (a list, not simply a number) are useful for clients to recycle as bootstrap nodes next time they connect. It's up to clients to decide which nodes...