Just as an FYI: Cloudflare challenges don't require you to add any js on your website. It's a layer that's built on their side.
It's sad to see that the decision is to downgrade the quality of the offered services because of this. What's the biggest problem here? Is it that you want to prevent crawlers accessing your content or reduce infra costs? I don't think crawlers are going to stop, they will probably become worse (e.g. see the new efforts from cloudflare to design new crawling agents that run at scale). Closing your eyes now will give you some immediate breathing room but I think it will just end up isolating you and making this community even more difficult to access. Best, Rolando On Sat, Aug 8, 2026 at 1:58 PM Mario Domenech Goulart <[email protected]> wrote: > Hi Rolando, > > On Sat, 8 Aug 2026 13:42:12 -0700 Rolando Abarca <[email protected]> > wrote: > > > I recently got hit on my own forgejo instance with bots crawling my > > fork of chicken-core. I have my instance behind cloudflare (free), so > > I added a challenge for the expensive routes and it stopped > > them. Wouldn't something like that work for call-cc.org? > > We have decided not to use those challenge-based approaches to protect > our pages because they normally require JavaScript on the client side. > Other solutions not based on JavaScript are also possible, but they tend > to be a hassle for infrastructure maintainers to deploy/maintain and for > users to make use of the resources. > > Our approach to deal with this mess is to simplify our services in a way > that we hopefully do not reduce the amount of material we provide, but > present them in a way that might be difficult for the plague of LLM > crawlers to abuse, and at the same time convenient enough for our target > audience to consume. > > All the best. > Mario > -- > https://parenteses.org/mario >
