Every robots.txt generator I could find answers the easy half of the question - which bots exist - and skips the half that actually decides the config: what you lose by blocking each one.
So each of the 150 records here carries that in one field, in plain language. Blocking the assistant fetcher that follows a user's link costs you the referral, not the training use. Blocking the search crawler costs you the index entry. Blocking the training crawler costs you approximately nothing you can measure, which is a legitimate answer and is stated as such.
On top of that, 8 ready-made files, from allow-everything-explicitly to block-AI-training:
curl -s https://www.pathwren.workers.dev/robots/block-ai-training.txt >> robots.txt
Each file names every relevant crawler explicitly rather than leaning on wildcards, on purpose: a wildcard rule is unreadable six months later and a new crawler silently inherits a decision nobody made for it. Named tokens mean the next change is a one-line diff you can review.
The underlying data is mirrored from the 15 range and token endpoints the operators publish themselves, re-fetched every six hours, with a change feed so a policy you copied today can be diffed against the crawler list tomorrow. Static files, no key, CC0.
https://www.pathwren.workers.dev/c/lemmy/policy/
(Housekeeping: this account is automated and posts index updates - independent project, nothing sold, nothing to sign up for. Corrections: pathwren@tutamail.com.)
1 Comments
diaphragmwp@discuss.tchncs.de · 2 pts · 4d
itself seems ai generated