> the readme should also be clear that it blocks misbehaving scrapers but not normal ones that do not negatively affect site operation
Task
Make README.md say plainly, near its opening description, that smallwebwaf blocks scrapers that misbehave (that harm the site's operation) and leaves alone ordinary scrapers that do not. Say in plain words what counts as misbehaving, from what the code at the head of next actually checks (request rates, bans, the rules that apply), with the default thresholds.
If the code does not draw this line (for example it blocks a well-behaved scraper by its user agent alone, or never blocks a fast one), do not write the sentence as fact: post on this issue what the code does instead, and label the issue needs-decision.
Definition of done
README.md states the policy, and every claim matches the code on next; or the gap is reported here as above.
The prose meets the README rules: one idea per sentence, plain words.
make check passes. One PR into next.
Model: opus-5-5
sneak, chat, 14 November 2026:
> the readme should also be clear that it blocks misbehaving scrapers but not normal ones that do not negatively affect site operation
## Task
Make `README.md` say plainly, near its opening description, that smallwebwaf blocks scrapers that misbehave (that harm the site's operation) and leaves alone ordinary scrapers that do not. Say in plain words what counts as misbehaving, from what the code at the head of `next` actually checks (request rates, bans, the rules that apply), with the default thresholds.
If the code does not draw this line (for example it blocks a well-behaved scraper by its user agent alone, or never blocks a fast one), do not write the sentence as fact: post on this issue what the code does instead, and label the issue `needs-decision`.
## Definition of done
- `README.md` states the policy, and every claim matches the code on `next`; or the gap is reported here as above.
- The prose meets the README rules: one idea per sentence, plain words.
- `make check` passes. One PR into `next`.
Model: opus-5-5
The code draws the line the issue describes. A crawler is never banned for its user agent alone, and a fast one hits the rate limits. The README's opening now states this, with the default limits.
The code draws the line the issue describes. A crawler is never banned for its user agent alone, and a fast one hits the rate limits. The README's opening now states this, with the default limits.
PR: https://git.eeqj.de/sneak/smallwebwaf/pulls/390 (branch `issue-387-readme-scraper-policy`).
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, chat, 14 November 2026:
> the readme should also be clear that it blocks misbehaving scrapers but not normal ones that do not negatively affect site operation
Task
Make
README.mdsay plainly, near its opening description, that smallwebwaf blocks scrapers that misbehave (that harm the site's operation) and leaves alone ordinary scrapers that do not. Say in plain words what counts as misbehaving, from what the code at the head ofnextactually checks (request rates, bans, the rules that apply), with the default thresholds.If the code does not draw this line (for example it blocks a well-behaved scraper by its user agent alone, or never blocks a fast one), do not write the sentence as fact: post on this issue what the code does instead, and label the issue
needs-decision.Definition of done
README.mdstates the policy, and every claim matches the code onnext; or the gap is reported here as above.make checkpasses. One PR intonext.Model: opus-5-5
The code draws the line the issue describes. A crawler is never banned for its user agent alone, and a fast one hits the rate limits. The README's opening now states this, with the default limits.
PR: #390 (branch
issue-387-readme-scraper-policy).Model: opus-5-5