Weighs the soul of incoming HTTP requests to stop AI crawlers

docs(blog/v1.20.0): fix typo

Signed-off-by: Xe Iaso <me@xeiaso.net>

Xe Iaso 19f78f37 b0b0a5c0

+1 -1
+1 -1
docs/blog/2025-06-27-release-1.20.0/index.mdx
··· 51 52 This is different from the past where you could only allow every request with a Gitea session token, meaning that the invention of lying would allow malicious clients to bypass protection. 53 54 - Weight is added and removed whenever a `WEIGH` rule is encountered. When all rules are processed and the request doesn't match any `ALLOW`, `CHALLENGE`, or `DENY` rules, Anubis uses [weight thresholds](docs/admin/configuration/thresholds) to figure out how to handle that request. Thresholds are defined in the [policy file](/docs/admin/policies) alongside your bot rules: 55 56 ```yaml 57 thresholds:
··· 51 52 This is different from the past where you could only allow every request with a Gitea session token, meaning that the invention of lying would allow malicious clients to bypass protection. 53 54 + Weight is added and removed whenever a `WEIGH` rule is encountered. When all rules are processed and the request doesn't match any `ALLOW`, `CHALLENGE`, or `DENY` rules, Anubis uses [weight thresholds](/docs/admin/configuration/thresholds) to figure out how to handle that request. Thresholds are defined in the [policy file](/docs/admin/policies) alongside your bot rules: 55 56 ```yaml 57 thresholds: