When thinking about building a secure, DDoS and censorship-resistant onion service, I've seen many implementations using compartmentalization (like Qubes AppVMs) of services and OnionBalance. Such approach may be good at mitigating service exploits, so that breaching the http or the db server-vm will not affect the rest of the website, but fails to provide true censorship resistance.
This is where solutions like ZeroNet or Tahoe-LAFS may come to help.

However, by doing so the lag problem arises. To maintain anonymity the onion routing protocol must be followed and, in order to retrieve the page, the user will have to wait for both the website backend reply and the data distributed over the aforementioned grids.

Is there an easier way to solve the lag problem without giving out anonymity?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.