DNSProxy: how to use TOR and stay "safe(r)"

RATIONALE

Here listed all upcoming improvements, emergency bugfixes, benchmarks and ... well ... disadvantages of DNSP Focus on:

anonimity
speed vs cache vs scaling
mantaining anonimity: no extra traces, how to de-patternize traffic, why using HTTP pipelining, etc..
concepts of "shareability" of resources or "the need of mantaining a network functional because of its shared need"
hide away - just DNT. this the P2P of DNS!!

add multiple online backends other than f.net/nslookup.php (-> avoid localhost "dev" support need, will easen life of average TOR user)
add interface between TOR routing and DNS query target (to avoid "split DNS" issues and make faster browsing, by sacrificyng almost no-privacy). yes, geobinding at least in major blocks, EMEA-US-PAC-RUS-AFNIC... TDB.
multiple auth ? OAUTH ? Shibboleth ?

the solution is based on cache, so the resource has to be hit at least once to profit from additional "speed".
the node has the option to spawn TCP/HTTP own relay, useful to TOR users (find best anonymous DNS in a RR fashion by choosing between available DNSP-relays or just wiki-alike ??). focus on flexibility and dynamicity of the TOR network, usage, resilience, etc.
benchmarking localhost VS remotes. like mixing apples and bananas... but cache may really be infinite !! -> our goal here is to unbind user from metadata, as DNS is. building a shared cache is useful but needs maintenance = risk for the ANON infra to be infiltrated..
benchmark always spots interesting stuff. do it.

See you online ! M