For me, I just have to check the box. I haven't been kicked back to it yet either, though I mostly just scroll through the /all tab to see if anything I care about has been updated

>>22500
Works ok for me. Are you using the site through ToR or a DNS / proxy?

>>22501

Good for you. As for me, it took me literally until next day until site finally loaded and now I'm just flacidly pressing checkbox-checkbox-checkbox-send checkbox-checkbox-checkbox-send to post this response.

>>22502

Yes, of course. Visiting this site over clearnet is literal death wish from my country.

On related note, it seems like .onion site no longer works as well.

I understand users from some parts of the world need Tor to feel comfortable accessing this site and an anti-botspam feature I enabled on cloudflare was inconvenient for them.
For the time being, I enabled a lesser level of protection and disabled the previous one, meaning you probably won't see that cloudflare check on Tor.

However, I can't promise not enabling it back in case of necessity in the future. I hope I won't need to do it anytime soon at least.

While I understand that it's necessary to protect a site ‒ esp. one like this ‒ against attackers, I also understand that Cloudflare is not very userfriendly. I'm not in danger in my country when visiting here. So I don't use a proxy. But as a basic level of anonymity I've disabled javascript and cookies. I appreciate that both are not needed here. OTOH, from Cloudflares point of view it transforms me into an evil sitemunching DDOS-spambot with an ancient browser, not even worth to be shown some basic information ‒ only a bunch of useless links, pointing more or less to itself and each other. Well, with a quick look in their source code, which gives you eye cancer because of that javascript spaghetti code, I found out who blocked me. BTW, it's amazing that these incidents always take place on a weekend ...

>>22509

Thank you, it appears to work for now.

If possible, it would be great if you could leave at least read-only access alive even if posting is protected by Cloudflare's loopy hell.

People are bitching Cloudflare at the gate seems to be gone and the spambots are back in full force, coincidence? I had no problems accessing the site with the low level Cloudflare it had.

>>22553

Agreed

>>22553

On plus side, there is actual content being posted now, which was mostly not the case while CF was active.

> I had no problems accessing the site with the low level Cloudflare it had.

I had.

>>22518
> ... leave at least read-only access alive ...
This is a good idea.

@kaguya: Is it possible?