Post
Topic
Board Meta
Re: Cloudflare now persistently requiring Javascript! (Here’s my temp mitigation.)
by
nullius
on 22/03/2018, 00:07:50 UTC
Cloudflare has effectually locked me out since sometime yesterday—both of me.  I am posting this from the account under which I first got hit with it, almost 22 hours ago.  This time, it does not stop!

Well, it seems to have subsided sometime between about 18:30 and 22:30 hours (UTC).  If theymos did anything to make Cloudflare back off, thank you.

I hope this will not happen again; though if it does, I now have shell scripts to help deal with it.  Whereas in the long term, for this and other reasons, everybody should hope a better anti-DDoS solution can be found.  Part of my own proposal would be a large mallet, applied to the heads of DDoSers.

An absolute requirement of Javascript will drive away many of the types of people whom the forum should want to attract:  Privacy and security experts, cypherpunks, people for whom the word “crypto” means something other than get-rich-quick schemes or Paypal 2.0.  For my part, it is unacceptable to me in the long term.





I have noticed an increased amount of "Try again later" errors during the repatcha solving process (where you have to select vehicles and street signs which Google seems to be obsessed with for some reason). Looks like Tor nodes are getting banned again at a higher rate.

See reference upthread; and if you have any information from your experience which may be helpful, perhaps consider documenting it for the benefit of others on the Google lockout thread.  I suggest that you check the box to stay logged in, and save your cookies.  Basic instructions are referenced on that thread; see also Meretrix’s shell script above.

...I made myself a dedicated Bitcoin Forum “thing” on the day that I was forced to try seventeen (17) different Tor circuits before Google deigned to grant me a login CAPTCHA.  See “Google is locking Tor users out of Bitcointalk.org!”.  One of my Newbie rank posts!