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?

Best,
Rolando Abarca


On Sat, Aug 8, 2026 at 1:23 PM Mario Domenech Goulart via Chicken-users <
[email protected]> wrote:

> Hi,
>
> In the recent years, CHICKEN has been facing a reality where the number
> of active maintainers is decreasing, and the load on the infrastructure
> and the effort to maintain it is increasing, mostly due to the new
> trends related to LLMs.
>
> As a reaction to that, we are simplifying our services to be able to
> keep them running as responsibly as we can with the resources we have,
> in a scenario where we have to take into account abuses from LLM
> crawlers.
>
> So far the current services have been simplified and, with that,
> limitations follow:
>
> * Gitweb, which provided an interface to browse the git repositories
>   hosted at call-cc.org, has been disabled and replaced with a much more
>   limited interface based on static HTML files:
>   https://code.call-cc.org/githtml/ .
>
> * The more featureful web interface to browse the SVN repository,
>   provided by Trac, has also been disabled.
>   https://code.call-cc.org/svn/chicken-eggs/ is still available
>   (anonymous login with empty password), but provides a much more
>   simplified interface.
>
> * The history of pages in our wiki, previously available through its web
>   interface, has been disabled.  Since the backend storage of the wiki
>   is SVN, history is still available if you check out the SVN
>   repository.  Being SVN, partial checkouts are possible.
>
> * The bug tracker, Trac, has been replaced with tick
>   (https://wiki.call-cc.org/eggref/5/tick), a tool we have developed to
>   keep track of CHICKEN issues.  As with web interface for git
>   repositories, tickets are now available in read-only format as static
>   HTML pages at Trac's previous location (https://bugs.call-cc.org/).
>   The basic URLs to view tickets have been preserved, including the
>   mapping to Trac ticket ids.  The documentation on how to report issues
>   has been updated: https://wiki.call-cc.org/support
>
> * Not yet done, but we will shut down paste.call-cc.org.  Although it is
>   convenient and is a practical CHICKEN application, it is not deemed
>   essential to our infrastructure and is currently unmaintained.  If you
>   want to maintain and host it, feel free to reach out and we'll make
>   paste.call-cc.org resolve to your server.
>
> Apologies in case these changes cause any inconvenience to your
> workflows.
>
> All the best.
> Mario (on behalf of the CHICKEN team)
> --
> https://parenteses.org/mario
>
>

Reply via email to