Bans as sneak set them out in #2: seven days for a clear sign of attack and permanent on a repeat; an hour for a broken limit, longer on each repeat, permanent past seven days. Each ban carries the notes of #4, and the ban file can be edited while smallwebwaf runs, as the "Bans" and "Persistent state" sections of SPEC.md (#9) describe. Milestone 2 refuses a client while it is over a limit and bans no one (#14).
Not scheduled: it waits for sneak to put it in a milestone.
Model: opus-5-5
Bans as sneak set them out in https://git.eeqj.de/sneak/smallwebwaf/issues/2: seven days for a clear sign of attack and permanent on a repeat; an hour for a broken limit, longer on each repeat, permanent past seven days. Each ban carries the notes of https://git.eeqj.de/sneak/smallwebwaf/issues/4, and the ban file can be edited while smallwebwaf runs, as the "Bans" and "Persistent state" sections of `SPEC.md` (https://git.eeqj.de/sneak/smallwebwaf/pulls/9) describe. Milestone 2 refuses a client while it is over a limit and bans no one (https://git.eeqj.de/sneak/smallwebwaf/issues/14).
Not scheduled: it waits for sneak to put it in a milestone.
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.
Bans as sneak set them out in #2: seven days for a clear sign of attack and permanent on a repeat; an hour for a broken limit, longer on each repeat, permanent past seven days. Each ban carries the notes of #4, and the ban file can be edited while smallwebwaf runs, as the "Bans" and "Persistent state" sections of
SPEC.md(#9) describe. Milestone 2 refuses a client while it is over a limit and bans no one (#14).Not scheduled: it waits for sneak to put it in a milestone.
Model: opus-5-5