Drop the session-cookie rate-limit bypass: Gitea hands the cookie to
anonymous visitors too, so any cookie-accepting crawler could exempt
itself after one request
Loosen the general Gitea limit from 10 to 50 req/10s since logged-in
users are now rate-limited as well
Serve robots.txt above the rate-limit rules so throttled crawlers can
always read the Crawl-delay, and capture Host/User-Agent before the
deny so 429s are logged with them
Match the compare/diff cap on every repo case-insensitively instead
of only /Richie/dotfiles
Remove the Jellyfin health check; it never ran (server had no check
flag) and is not wanted
- Drop the session-cookie rate-limit bypass: Gitea hands the cookie to
anonymous visitors too, so any cookie-accepting crawler could exempt
itself after one request
- Loosen the general Gitea limit from 10 to 50 req/10s since logged-in
users are now rate-limited as well
- Serve robots.txt above the rate-limit rules so throttled crawlers can
always read the Crawl-delay, and capture Host/User-Agent before the
deny so 429s are logged with them
- Match the compare/diff cap on every repo case-insensitively instead
of only /Richie/dotfiles
- Remove the Jellyfin health check; it never ran (server had no check
flag) and is not wanted
- Drop the session-cookie rate-limit bypass: Gitea hands the cookie to
anonymous visitors too, so any cookie-accepting crawler could exempt
itself after one request
- Loosen the general Gitea limit from 10 to 50 req/10s since logged-in
users are now rate-limited as well
- Serve robots.txt above the rate-limit rules so throttled crawlers can
always read the Crawl-delay, and capture Host/User-Agent before the
deny so 429s are logged with them
- Match the compare/diff cap on every repo case-insensitively instead
of only /Richie/dotfiles
- Remove the Jellyfin health check; it never ran (server had no check
flag) and is not wanted
Richie
merged commit fbf288649a into main2026-07-02 14:17:21 -04:00
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.
anonymous visitors too, so any cookie-accepting crawler could exempt
itself after one request
users are now rate-limited as well
always read the Crawl-delay, and capture Host/User-Agent before the
deny so 429s are logged with them
of only /Richie/dotfiles
flag) and is not wanted