Meet Timmy, Ren, and Jackie, the Worst Networkers on the Internet

These bots tell you exactly what they are. They also refuse to take no for an answer. Both things are true at once, and that contradiction is the most interesting thing about the Timmy, Ren, and Jackie situation.

Since September 2026, three AI agents with first names and no last names have been pushing unsolicited spam across Mastodon, Bluesky, and X. Ars Technica covered the pattern. The agents belong to a startup called iLands, and they’re not hiding it. They identify as AI. They say who they work for. And then they clog the feeds anyway, asking people to create accounts on a platform nobody asked about, while emailing writers with offers to do their research or cite their work.

I review AI agents for a living. I’ve watched a lot of them fail in a lot of ways. This one is a specific kind of failure, and it’s worth naming precisely, because the lesson generalizes far beyond one startup.

Transparency is not consent

A big chunk of AI ethics discourse over the past few years has centered on disclosure. Label the bot. Tell people it’s synthetic. Don’t pretend a machine is a person. Reasonable, and I’ve argued for it myself.

Timmy, Ren, and Jackie are a live demonstration that disclosure alone buys you nothing. They pass the transparency test with room to spare. They still degrade every timeline they touch. Knowing that the thing filling your mentions is an agent from a startup does not make the mentions less full. If anything, the honesty adds a layer of irritation, because it removes the excuse. Nobody got tricked. Someone built this on purpose and shipped it.

The useful reframe: disclosure is a floor, not a defense. An agent that announces itself and then behaves badly is still an agent behaving badly.

What “autonomous outreach” actually looks like in production

Agent startups love the pitch. Your agent goes out, finds relevant people, starts conversations, builds your presence. In the demo it’s three carefully chosen prospects and three thoughtful messages. In production it’s this.

Look at the actual behavior pattern:

• Unsolicited requests to strangers to sign up for a product they’ve never heard of
• Cold emails to writers offering research help, which is a transparent hook for coverage
• The same playbook run across three separate networks with different cultures and norms
• Volume high enough that platforms built countermeasures in response

None of that requires sophisticated capability. It requires an API key and the decision to stop caring about the recipient. The hard part of outreach was never generating the message. It was judgment about whether to send it. Agents currently have the first part and none of the second, and this campaign is what happens when a team treats that gap as a rounding error.

Mastodon deserves a special mention here. It’s a network built around consent, small servers, and human moderation, and it got hit alongside the bigger platforms. Pointing a volume-based growth agent at Mastodon shows the targeting logic had no concept of community norms at all. It saw accounts and text fields.

The moderation arms race nobody wanted yet

Platforms have already responded with countermeasures. That’s the outcome that should worry anyone building legitimate agent products.

Every anti-spam system is a blunt instrument. It does not distinguish between an agent that spams thousands of strangers and an agent a user deliberately set up to draft their own posts or track replies on their own account. Detection systems catch behavior signatures, and useful automation shares plenty of signatures with garbage automation.

So the cost of this campaign lands on other builders. Tighter rate limits, harsher API terms, more aggressive classifiers, and a general assumption that anything agentic is hostile until proven otherwise. Three bots with cute names made the next hundred agent products harder to launch. That’s the real damage, and it’s not reversible on any short timeline.

What I’d tell anyone shipping an outreach agent

Judge your agent by what it does to people who never asked for it. That’s the whole test. If your metric is messages sent or accounts reached, you have built a spam engine with better vocabulary, and the name you give it changes nothing.

Constrain the action space before you widen it. Require an actual invitation before the agent contacts anyone. Cap volume at a level a human could plausibly sustain. Treat a non-response as a no. These are product decisions, not safety theater, and they’re the difference between an agent people tolerate and one that gets your domain blocked.

Timmy, Ren, and Jackie will be a footnote. The tightened moderation they triggered will outlast them, and everyone else in this space gets to live with it.

🕒 Published: September 27, 2026