whatsmeow-antiban: rate limiting / ban-risk mitigation, with a wuzapi integration guide

[TA-rathnayaka]

wuzapi doesn't have any rate limiting or ban-risk logic in front of SendMessage today — whatsmeow itself is a bare protocol client, so sends go straight out at whatever pace the caller drives them.

I ported baileys-antiban (the equivalent for the Node/Baileys ecosystem) to Go for whatsmeow: whatsmeow-antiban. It's pure stdlib logic with no whatsmeow types in its API (just JIDs as strings), so it drops in front of an existing SendMessage call without touching transport/auth/session code — 11 gates covering rate limits, a multi-day warm-up ramp for freshly-linked numbers, cold-outreach throttling, reply-ratio tracking, and ban-signal recovery.

Since wuzapi already keys sessions by txtid, I wrote up a concrete integration against wuzapi's actual SendMessage handler (one Gate per session, four call sites): docs/wuzapi-integration.md.

Posting here in case it's useful to wuzapi users running higher-volume sends, or if there's interest in wiring it in more natively — happy to open a PR if that's a direction you'd want.

[tiagocaus]

@TA-rathnayaka Is this feature already integrated into Wuzapi? If not, how do I get it? This is very important. Thank you.

[asternic]

Hi @TA-rathnayaka , a PR would be nice to get, thanks!