- Rust 84.7%
- Nix 13.1%
- Just 2.2%
43047a4b9eTemporarily drop support for script config files, and require script configuration to be in-line. The reason for this is that `Blueprint` must remain search-path agnostic, yet, it tried to load the file immediately, which isn't what we want in the long run. |
||
|---|---|---|
| .forgejo | ||
| iocaine | ||
| iocaine-label | ||
| iocaine-powder | ||
| iocaine-recipe | ||
| iocaine-table | ||
| LICENSES | ||
| nix | ||
| share/etc | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| flake.lock | ||
| flake.nix | ||
| justfile | ||
| README.md | ||
| REUSE.toml | ||
iocaine
The deadliest poison known to AI.
Warning
This is the development branch of iocaine, and contains breaking changes, and will continue breaking unexpectedly. We recommend using the stable branch in production.
Iocaine is a defense mechanism against unwanted scrapers, sitting between upstream resources and the fronting reverse proxy. It is designed to significantly reduce the load caused by the relentless attack of the Crawlers (mostly originating from various AI companies) in a way that does not place undue burden on benign visitors. While iocaine does support presenting a proof-of-work challenge, that should be a last resort, and even if that path is taken, the challenge is inexpensive for the human visitor.
Originally, iocaine started as a garbage generator, a tarpit, a place where the reverse proxy routed unwanted visitors, so that they'd crawl an infinite maze of garbage. Since then, it grew into a more ambitious project, and includes a scripting engine that lets the iocaine-operator tell the software how to treat each incoming request. The idea remained similar, however: keep the crawlers in the maze, and let the backend serve the real content for benign visitors.
Unlike some similar tools, iocaine does not try to make the bad bots go away, it welcomes them, into an infinite maze of garbage. It does so, because that makes it possible to serve them poisoned URLs, which in turn, makes it possible to identify bad actors even if they come back piggy-backing on a real browser. By filling their queue with junk when they visit with their simpler collectors, we can capture the browser-based scrapers in the maze too.
The garbage generator in iocaine has been engineered to require as few resources as possible, to keep it cheap, pretty much on par with serving a static file from the filesystem. The goal is to have a tool that costs next to nothing for the operator, reduces the load on upstream services, and protects them from the crawlers, while having no (or at worst, very little) effect on legit visitors, but making life of crawler operators difficult at the same time.
For more information about what this is, how it works, and how to deploy it, have a look at the dedicated website.
Lets make AI poisoning the norm. If we all do it, they won't have anything to crawl.
Sponsorship + Funding
Crowdfunding
If you would like to donate to @algernon to keep the lights on during development, you can do so via Liberapay. Other donation options are available too, feel free to contact him.
NLnet
This project is receiving funding through NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.
