But they did discuss trying to reduce the impact some months ago, and
a few weeks ago there was a regression which they were working on
addressing. It seems that they actually have improved the situation.

That is interesting. Are there any public sources on this with more technical details?

I'd like to understand what exactly has changed.

Actually, I think that if the change they did makes sense technically (at least it has a good effect), we can probably use that as a positive example to show to other CDNs / hosting providers / etc.

Maybe a blog post about this in the tor project's blog would even make sense.

Because there's a lot of discussion about how bad CloudFlare was with the captchas, but not really anything that I could find easily about positive changes they did.

I think it's important to highlight improvements when they happen.

On 2018-03-08 18:59, Dave Warren wrote:
That might be part of it, but I just fired up a fresh Tor browser,
opened half a dozen sites that used to always require a CAPTCHA and
none did. I haven't used Tor in a couple weeks, so I'm not really sure
when this started.

But they did discuss trying to reduce the impact some months ago, and
a few weeks ago there was a regression which they were working on
addressing. It seems that they actually have improved the situation.


On 2018-03-08 10:38, Watson Ladd wrote:
Blinded tokens finally shipped. As a result they can remember that you
solved the captcha.

On Thu, Mar 8, 2018 at 5:15 AM,  <ther...@firemail.cc> wrote:
Recently I've realized that I'm not seeing the CloudFlare capchas anymore in
TBB, or seeing them far less often.

Is it just me, or they have really changed something about their captchas?
--
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



--
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

Reply via email to