Did you actually try to access CloudFlare through a text-only browser? Try it. `$ lynx http://ietf.org/` It works perfectly fine for me. CloudFlare only /conditionally/ presents the captcha when it determines a need. The only place I've ever seen that happen is using Tor. You really don't need JavaScript unless you get caught by their rules (e.g. Tor and maybe some NATs?) otherwise it won't bother you. Regards, Tom Thorogood. [Disclosure: I'm a completely satisfied CloudFlare client of several years.] On 17/09/14 03:11, Rich Kulawiec wrote: > On Tue, Sep 16, 2014 at 01:52:32PM +0200, Linus Nordberg wrote: >> This is sad because it's now not possible to visit the site without >> accepting JavaScript. > > That effectively breaks the site for anyone using a text-only browser > or for anyone who (wisely) uses a browser add-on like NoScript. [1] While > the use of JavaScript for *some* web site functions is reasonable, any > web site that doesn't provide basic functionality (including navigation) > without it is, in my opinion, completely inadequate for professional use. > > ---rsk > > [1] Yes, such users can temporarily un-break it by allowing NoScript > to execute for the particular domain/hostname in question, however > my experience with Cloudflare is that one must permit a random-looking > Cloudflare hostname. This provides little assurance that the same > hostname will work in the future, nor is there any indication of which > additional sites might be associated with that hostname -- and thus > which a user may be unwittingly permitting to run JavaScript. >