I have a fairly low-bandwidth application, which is using dynamic DNS style lookups to allow people to access an automation hub at home, when they are on-the-go.
On the server side of things, OpenDHT seems like a perfect choice, but on a mobile device it could easily use up an entire user's data plan to run a full node.
Everything is completely open source, and I expect that most people should almost never need to use the proxy servers, probaby not even once, as there is aggressive caching and local discovery.
But it seems that the public DHT server is a subdomain of Jami, and I haven't seen any official ToS for making requests from other applications. Does such a policy exist?
ghenry
commented
2 years ago
I have a fairly low-bandwidth application, which is using dynamic DNS style lookups to allow people to access an automation hub at home, when they are on-the-go.
On the server side of things, OpenDHT seems like a perfect choice, but on a mobile device it could easily use up an entire user's data plan to run a full node.
Everything is completely open source, and I expect that most people should almost never need to use the proxy servers, probaby not even once, as there is aggressive caching and local discovery.
But it seems that the public DHT server is a subdomain of Jami, and I haven't seen any official ToS for making requests from other applications. Does such a policy exist?