Twitter account got flagged as bot

[rabden]

Version

0.6.0

Operating System

Linux

Browser (for cookie extraction)

Brave

Access Method

Local terminal

What happened?

My Twitter account was flagged as a bot, which has significantly reduced my account visibility.ed my account visibility.

Expected behavior

Dont know, not get my account flagged

Steps to reproduce

reply to a few people everyday

Diagnostics

Error output / logs

[qdang46]

Hi — I'm the author of a Rust port of this tool, twr. Can't fix someone else's flagged account, but the ban-risk posture this issue is really about is designed into twr from the start: browser-matched TLS fingerprinting (never plain reqwest), request jitter + 1.5–4s write delays with a floor agents can't tune below, conservative default fetch sizes, a local daily mutation budget (default 200, exit 2 when exceeded, never fully disableable), and --policy read_only so read-only agent tasks structurally cannot post. The sanctioned zero-risk path (official API v2, per #21) exists there as a feature-gated --backend api-v2. Real talk, same as upstream would tell you: cookie automation always carries residual risk — these are mitigations, not immunity.