You might be interrested in why libcurlpp, json and libb64 are needed for dpaste. dpaste actually supports using an http server frontend to opendht (see version 0.3.0 msg). Therefore, you might want to consider packaging the http server (depending on python wrapper around opendht) with an appropriate daemon service file. If dpaste runs using the http frontend, the user gains speed and actually actively contributes to the DHT network. Otherwise, dpaste always creates a DHT node for executing its operations and destroys it upon completion.
Nice! Thanks for this contribution!
You might be interrested in why libcurlpp, json and libb64 are needed for dpaste.
dpasteactually supports using an http server frontend to opendht (see version 0.3.0 msg). Therefore, you might want to consider packaging the http server (depending on python wrapper around opendht) with an appropriate daemon service file. If dpaste runs using the http frontend, the user gains speed and actually actively contributes to the DHT network. Otherwise, dpaste always creates a DHT node for executing its operations and destroys it upon completion.