On Wed, Nov 19, 2014 at 01:01:37PM +0100, Fabio Pietrosanti - lists wrote: > > On 11/19/14 12:39 PM, onion.lt admin wrote: > > I do not agree with a hardcoded block for facebook. If tor2web.org wants > > to block facebook, add it to the block list, but do not assume blocking it > > wholesale protects people in any and all scenarios. > > > > It also sets a very bad example with regard to 'censorship'. > > > > Any other sites that receive a hardcoded 'special treathment' ? > > There's no hardcoded block in Tor2web software, this is the default > facebook page when detect the X-Tor2web: HTTP header.
Good to know. Is there a way to disable the X-Tor2web header ? (option in tor2web.conf: "Hide-X-Tor2Web-Header: True/False") > Instead Tor2web, with the latest release, started supporting access to > "https" based .onion sites, such as the first has been Facebook. Which is great! > But Facebook, want reasonably to prevent access from Tor2web users and > that's fine, it's their choice, not our own! Yes that is their choice, however I do not see a reason to enable a hidden_service to know if a visitor came from Tor or via Tor2web. Another question. Can you make it possible for the template directory to override the defaults if it is available at /home/tor2web/templates ? Tnx! -- [email protected] | dizum.com - The Internet Problem Providers. _______________________________________________ Tor2web-talk mailing list [email protected] http://lists.globaleaks.org/mailman/listinfo/tor2web-talk
