The ban records in JSON need to include a notes field that give detailed information about why the ban was created and include full context such as the name the AS name and the country and the number of requests that caused the ban, the number of requests that were made total from that net block, even post ban, the time window over which the inappropriate requests were being made, and any other information that an min may use to decide whether or not that net block should be unbanned in the future. How many times it had been short-term banned, etc the state files are going to need to include a fair amount of information about legitimate requests and net blocks so that the server on restart can load that back into memory and be able to provide detailed stats about the history of a net block, including those that are not banned.
The ban records in JSON need to include a notes field that give detailed information about why the ban was created and include full context such as the name the AS name and the country and the number of requests that caused the ban, the number of requests that were made total from that net block, even post ban, the time window over which the inappropriate requests were being made, and any other information that an min may use to decide whether or not that net block should be unbanned in the future. How many times it had been short-term banned, etc the state files are going to need to include a fair amount of information about legitimate requests and net blocks so that the server on restart can load that back into memory and be able to provide detailed stats about the history of a net block, including those that are not banned.
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of #6, adds a notes field to every ban record. It carries the full context an admin needs to decide on an unban:
the AS name and the country;
the requests that caused the ban;
the netblock's total requests, including those after the ban;
the time window of the bad requests;
how many short bans came before.
The state files also keep each netblock's history of legitimate traffic, including netblocks that were never banned. They are loaded back at start, so the detailed per-netblock stats survive a restart.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
Model: opus-5-5
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of https://git.eeqj.de/sneak/smallwebwaf/issues/6, adds a notes field to every ban record. It carries the full context an admin needs to decide on an unban:
- the AS name and the country;
- the requests that caused the ban;
- the netblock's total requests, including those after the ban;
- the time window of the bad requests;
- how many short bans came before.
The state files also keep each netblock's history of legitimate traffic, including netblocks that were never banned. They are loaded back at start, so the detailed per-netblock stats survive a restart.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
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.
The ban records in JSON need to include a notes field that give detailed information about why the ban was created and include full context such as the name the AS name and the country and the number of requests that caused the ban, the number of requests that were made total from that net block, even post ban, the time window over which the inappropriate requests were being made, and any other information that an min may use to decide whether or not that net block should be unbanned in the future. How many times it had been short-term banned, etc the state files are going to need to include a fair amount of information about legitimate requests and net blocks so that the server on restart can load that back into memory and be able to provide detailed stats about the history of a net block, including those that are not banned.
Recorded. Sorry this sat for two days without an answer.
The spec update, the folding unit of #6, adds a notes field to every ban record. It carries the full context an admin needs to decide on an unban:
The state files also keep each netblock's history of legitimate traffic, including netblocks that were never banned. They are loaded back at start, so the detailed per-netblock stats survive a restart.
The repo is paused under the 2026-09-22 priority ruling. The unit runs when the repo resumes, and its PR closes this issue.
Model: opus-5-5
clawbot referenced this issue2026-09-23 14:47:13 +02:00
Closed by the merge of #9 into
next(commit7898957).Model: opus-5-5