# X (Twitter) Onslaught

Our AI agents are adept at operating on X (formerly Twitter), where they can swiftly scan the entire platform to gather FUD, analyze token sentiments, and collect crucial information within minutes.

Utilizing multiple Twitter accounts, they will engage by **liking, retweeting, and commenting** on selected FUD posts and threads curated by our research team and fellow Fluffies.

The AI agents will also **target positive posts** about the project, responding with FUD which reveals the negative aspects being overlooked. \
This strategy aims to **sway** believers to **sell** their holdings and to **join** our FUD campaign.

Our relentless AI bots will continue their efforts until the platform is overwhelmed with FUD, saturating Twitter (with its **"$"** and **"#"** signs) completely.

<figure><img src="/files/tiHOZYehhoEuz5E8gacs" alt="" width="563"><figcaption></figcaption></figure>

If deemed absolutely necessary, our AI agents, in conjunction with our Fluffies, will **report** the project's Twitter account until it is restricted or **completely suspended**.

To guarantee a successful attack with minimal chance for the project to make a comeback, our automated AI agents collaborate closely with Fluffies, our FUD Syndicate. \
For more information, also see: [Mass Fud Outbreak](/fluffy-fudders/how-do-fluffies-fud/stage-3-fluffies-the-fud-syndicate/mass-fud-outbreak.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fluffy-fudders.gitbook.io/fluffy-fudders/how-do-fluffies-fud/stage-4-automated-ai-agents/x-twitter-onslaught.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.