4 Commits

Include renames

Author	SHA1	Message	Date
pmb	1bfbcfdac3	Add welcomebot-reputation CLI and a --reputation log filter ... The pre-signup path had no inspection tool. Its activity landed in docker logs and two sqlite tables with nothing to read them, while the reactive path has had welcomebot-signups and welcomebot-suspicious all along. welcomebot-reputation reads reputation_query and reputation_block directly so it survives log rotation: recent answers, --stats for volume and flag/block rate by source, --blocks for what is actually in force, and --deferred to see whether the hourly provider-lookup ceiling is biting. --blocks marks rows GONE once the reconcile pass finds the block no longer on the Mastodon side, so "we installed this" and "this is in force" stay distinguishable. welcomebot-logs --reputation covers the raw lines (pre-blocks, budget refusals, width-cap narrowings).	2026-09-13 16:35:11 -07:00
pmb	0356fe7997	Replace RDAP/ipwhois signup-IP classifier with ipapi.is ... Flags datacenter, vpn, proxy, tor, and independently-scored abuser signals instead of regex-matching RDAP org names; anonymous tier covers 1000 req/day, well above signup volume.	2026-07-06 08:57:55 -07:00
pmb	0a196c3788	Add --ip filter to welcomebot-logs for signup-scrutiny decisions	2026-07-02 16:51:24 -07:00
pmb	c0e5df3cc4	Initial commit: welcome-bot, abuse-bot, dormant-sweep, IP signup scrutiny	2026-07-02 16:22:30 -07:00