> 2. Go to ipv4.google.com
> 3. search, captcha that will show up should be just text, and easier.
> This would've been easier if there was a NoScript blacklist where JS
> is always disabled, instead of constantly switching between security
Yes javascript.enable=false seems nicer (with "text image
> Looks like all connections from Tor exits by innocent Tor users
to Google"s search service are being treated by Google as
being lepers and are constantly force fed captchas so Google
can eat them as fois gras.
Work-around that I found to be somewhat acceptable:
1. Set high security setting,
2. Go
Jeremy Rand writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> My understanding is that the communication between circuit hops has
> forward secrecy, but I've been unable to find any documentation on
> whether forward secrecy exists for traffic sent between a Tor client
> and a Tor o
James Bunnell:
> grarpamp:
>
>> Fuck Google.
>>
>
> yes, agreed.
>
Smart. Open source smart. Beats giving a comparable service.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
grarpamp:
> Fuck Google.
>
yes, agreed.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
> Clearly you're an expert in fake profiles. I can't _imagine_ why FB would
> be blocking your accounts.
Facebook doesn't believe in free speech, or privacy, and as
industry typical, it cheaps out on more accomodating / enlightened
methods... so that's to be expected.
And a shame, since innocent
On Sun, Jun 18, 2017 at 1:39 AM, Roger Dingledine wrote:
>
> It looks like a growing number of connections from Tor exits are being
> treated by Google as being Ukrainian.
Looks like all connections from Tor exits by innocent Tor users
to Google's search service are being treated by Google as
bei
