Hi,
anonym wrote (27 Mar 2012 21:28:39 GMT) :
First of all, I just realized one thing the current implementation
breaks w.r.t. what we decided on IRC when we first discussed the
Unsafe Browser: the default button in the really start unsafe
browser-dialog is Yes, not No as we decided.
I was
Hi,
the hidden service (37lnq2veifl4kar7.onion) we've been configuring in
Tails to connect to OFTC since Tails 0.10.1 looks quite unreliable,
being sometimes down for days. On the other hand, connecting to OFTC
over Tor using the normal way these days requires changing circuits
a few times, but
03/28/2012 12:01 PM, intrigeri:
Hi,
the hidden service (37lnq2veifl4kar7.onion) we've been configuring in
Tails to connect to OFTC since Tails 0.10.1 looks quite unreliable,
being sometimes down for days. On the other hand, connecting to OFTC
over Tor using the normal way these days
03/28/2012 11:23 AM, intrigeri:
Hi,
anonym wrote (27 Mar 2012 21:28:39 GMT) :
First of all, I just realized one thing the current implementation
breaks w.r.t. what we decided on IRC when we first discussed the
Unsafe Browser: the default button in the really start unsafe
browser-dialog is
hello,
weasel runs the hidden service. I agree about changing the server back
away from the hidden service. Users will at least get a message about
being blocked from the network instead of receiving a SOCKS failure
when trying the downed .onion.
___
