iocaine 2.0.0

The deadliest poison known to AI
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86

iocaine
=======

[![Build status][ci:badge]][ci:url]
[![Container image][oci:badge]][oci:url]
[![Demo][demo:badge]][demo:url]
[![Documentation][docs:badge]][docs:url]

 [ci:badge]: https://git.madhouse-project.org/iocaine/iocaine/actions/workflows/build.yaml/badge.svg?style=for-the-badge&label=CI
 [ci:url]: https://git.madhouse-project.org/iocaine/iocaine/actions/workflows/build.yaml/runs/latest
 [oci:badge]: https://img.shields.io/badge/container-latest-blue?style=for-the-badge
 [oci:url]: https://git.madhouse-project.org/iocaine/-/packages/container/iocaine/latest
 [demo:badge]: https://img.shields.io/badge/demo-iocaine-seagreen?style=for-the-badge
 [demo:url]: https://poison.madhouse-project.org/
 [docs:badge]: https://img.shields.io/badge/docs-online-orange?style=for-the-badge
 [docs:url]: https://iocaine.madhouse-project.org/

> The deadliest poison known to AI.

This is a tarpit, modeled after [Nepenthes](https://zadzmo.org/code/nepenthes/), intended to catch unwelcome web crawlers, but with a slightly different, more aggressive intended usage scenario. The core idea is to configure a reverse proxy to serve content generated by `iocaine` to AI crawlers, but normal content to every other visitor. This differs from Nepenthes, where the idea is to link to it, and trap crawlers that way. Not with `iocaine`, where the trap is laid by the reverse proxy.

`iocaine` does not try to slow crawlers. It does not try to waste their time that way - that is left up to the reverse proxy. `iocaine` is *purely* about generating garbage.

For more information about what this is, how it works, and how to deploy it, have a look at the [dedicated website][docs:url].

Lets make AI poisoning the norm. If we all do it, they won't have anything to crawl.

Development
-----------

Assuming you have rust and cargo installed, you can build iocaine with:

```bash
cargo build
```

You can use the `maze-data/` directory to store your textual sources and configuration:

```bash
mkdir maze-data

# For convenience, we use the README as a markov source.
# A longer document would be better.
cp README.md maze-data/markov.txt

# Build a word list from the markov source
cat maze-data/markov.txt | tr -s ' ' '\n' | sed 's/[^a-Z]*//g' | sort | uniq > maze-data/words.txt

# Copy the templates for easier editing
cp -r templates/* maze-data/

# Create a config.toml file
cat > maze-data/config.toml <<EOF
[server]
  bind = "0.0.0.0:42069"

[templates]
  directory = "maze-data/"

[sources]
  words = "maze-data/words.txt"
  markov = ["maze-data/markov.txt"]

[generator]
initial_seed = ""
EOF

```
To build and run iocaine with your local changes, run:

```bash
cargo run -- --config-file maze-data/config.toml
```

If you have epubs around and `pandoc` installed, you can very easily build a word list and a markov source like this:

```bash
pandoc maze-data/*.epub -t plain > maze-data/markov.txt
cat maze-data/markov.txt | tr -s ' ' '\n' | sed 's/[^a-Z]*//g' | sort | uniq > maze-data/words.txt
```

Run tests with:

```bash
cargo test
```