From c226a886917b96d3755f843899602af2443623b0 Mon Sep 17 00:00:00 2001 From: Bob Mottram Date: Mon, 15 Feb 2016 09:23:10 +0000 Subject: [PATCH] Update website --- doc/EN/faq.org | 2 +- website/EN/backups.html | 6 +++--- website/EN/code.html | 8 +++---- website/EN/controlpanel.html | 2 +- website/EN/faq.html | 4 ++-- website/EN/index.html | 2 +- website/EN/installation.html | 2 +- website/EN/usage.html | 41 +++++++++++++++++++++++++++++++++++- 8 files changed, 53 insertions(+), 14 deletions(-) diff --git a/doc/EN/faq.org b/doc/EN/faq.org index c4a52746..6673f663 100644 --- a/doc/EN/faq.org +++ b/doc/EN/faq.org @@ -57,7 +57,7 @@ The source code for this project is experimentally independently hosted, and it Currently many of the repositories used for applications which are not yet packaged for Debian are on Github, and to provide some degree of resilliance against depending too much upon that it's possible to use [[./mirrors.html][mirrors stored on another server]]. * Why can't I access my .onion site with a Tor browser? -By default the Tor browser has [[https://www.eff.org/HTTPS-everywhere][https everywhere]] enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key). +Probably you need to add the site to the NoScript whitelist. Typically click/press on the noscript icon (or select from the menu on mobile) then select /whitelist/ and add the site URL. You may also need to disable HTTPS Everywhere when using onion addresses, which don't use https. * What is the best hardware to run this system on? It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you [[https://en.wikipedia.org/wiki/Uninterruptible_power_supply][UPS capability]] to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical. diff --git a/website/EN/backups.html b/website/EN/backups.html index 52b6cdd4..c4c6eb0a 100644 --- a/website/EN/backups.html +++ b/website/EN/backups.html @@ -3,15 +3,15 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - - + + + -