TWITTER_MAX_INTERACTIONS_PER_RUN is documented but never used

[myst4]

🐛 Bug Report

The plugin defines an environment variable:

TWITTER_MAX_INTERACTIONS_PER_RUN=10  # Maximum interactions processed per cycle

However, this value is never used anywhere in the code. Specifically, the handleTimeline() function retrieves 20 tweets via this.getTimeline(20), and for each tweet, the agent may perform up to 4 actions: [LIKE], [RETWEET], [QUOTE], [REPLY].

In practice, this can result in 40–60 actions being executed in a single run, all at once.

---

⚠️ Problem

• The defined variable maxActionsPerCycle = 20 inside the code is never enforced.
• The system does not limit or throttle the number of actions performed per run.
• All actions are executed immediately and in parallel, with no spacing or delay.
• This behavior may violate Twitter’s automation rules and can result in accounts being rate-limited or banned.

---

❓ Open Question

Given that TWITTER_MAX_INTERACTIONS_PER_RUN is documented as a limit, but not used anywhere in the code — is this an oversight, or is the intended behavior to handle rate-limiting differently?

Shouldn’t there be a safeguard in place to avoid executing dozens of actions in a single cycle?