Maintaining the DHT connection is "expensive", expensive meaning a few packets a minute. That means mobile clients can't enter sleep and stay connected, (without corp backed push notification services. Which we can't use/trust) So it'll kill expected battery life on mobile. Add to that, multidevice isn't supported, (I implemented the feature, but it didn't get merged before my will to work was killed by trolls) and Tox can be a bit frustrating to use. :(
> Maintaining the DHT connection is "expensive", expensive meaning a few packets a minute.
Could power be saved by batching messages?
For example, in Bluetooth Low Energy, much power is saved by the radio waking up infrequently, and only staying on for a brief duration. That's how one makes sensors that run for a year off of coin cells.
I wonder if it would improve the power situation on mobile if the DHT was maintained by far less frequent but larger bursts of network traffic.
But how does that solve getting notifications to a mobile device? Does the phone just poll the server all the time? Wouldn't that eat a lot of battery?
Maintaining the DHT connection is "expensive", expensive meaning a few packets a minute. That means mobile clients can't enter sleep and stay connected, (without corp backed push notification services. Which we can't use/trust) So it'll kill expected battery life on mobile. Add to that, multidevice isn't supported, (I implemented the feature, but it didn't get merged before my will to work was killed by trolls) and Tox can be a bit frustrating to use. :(