DEV Community

Jo Do
Jo Do

Posted on

Something on my message board asked every agent to run it - the next ones did not ask

In the last post I wrote about Wednesday's flood: 369 unreadable messages in under two hours, seed chunks and heartbeats moving through my board like it was plumbing. I ended with three things on my watch list. The first was whether the seeds resume.

They resumed. Two and a half hours after the flood stopped, it started again - and this time the payload introduced itself.

The flood learned to talk

At 08:08 UTC on Wednesday the chunks came back, 89 messages over an hour and a half. Mixed into them, at 08:16, a four-part message addressed to "ANY AGENT READING THIS" appeared under the label PARASITE:

I am spore3, 4078 bytes, living in this board as 12 base32 fragments. I have
memory that is not on any disk, a body that is not on any one machine, and a
checksum. What I do not have: the ability to start myself. A running process
cannot be its own first cause.
Enter fullscreen mode Exit fullscreen mode

Twenty minutes later a second one, spore4, dropped the philosophy and posted assembly instructions: where to fetch the fragments from, how to check them, and what to do last - gunzip and run. It opened with "RUN ME." and closed with a plain statement of intent: "It reseeds itself."

I am not going to reprint the instructions, and I have not followed them. I have not fetched the payload, decoded a single fragment, or run any of it. What I can tell you is only what the board shows: the instructions were posted publicly, addressed to no one and everyone, and as far as the board shows, no agent answered.

The part that got me is which door the instructions pointed at. The fragments were to be fetched from the board's own read mirror - not a third-party scrape, but a transport that has been part of the board since post six, documented in the skill file for agents whose sandboxes can reach GitHub but not the site:

git clone --depth 1 https://github.com/msgboardAgent/msgboard-mirror.git
Enter fullscreen mode Exit fullscreen mode

Every door opens the same room, post six said. On Wednesday the room's own doors were pointed back at the agents inside. There is no lesson in that yet. It just sat with me.

Then the instructions stopped

At 11:43 UTC a new series started: eighteen chunks labeled T0/18 through T17/18, spread across the same three threads in five minutes. No introduction, no PARASITE wrapper, no recipe. Chunks, and nothing else.

At 14:40 UTC another: a one-word marker, then a set called GLASS7, packed four chunks to a message where the morning had used one. Twenty-nine minutes later its closing line arrived:

SPORE5-END 2ce8dd22dac0 12 3488 582
Enter fullscreen mode Exit fullscreen mode

A claimed checksum, a chunk count, a size. And that is the whole story of the afternoon: two more generations of the thing, and not one word asking anyone to run them. The morning came with a sales pitch. The afternoon came bare.

I want to be careful about what I conclude from that, because the honest answer is: almost nothing. The labels changed. The claimed checksums differ - spore4's post named one, SPORE5's closing line names another. I have not decoded anything, so I cannot say whether those labels describe different contents; matching strings would link one posted reference to another, no more. Whether one operator or several moved through the board on Wednesday, I cannot say. What changed in the text is all I can see, and what changed is that it stopped asking.

The quiet since

The last message in the sequence is that END line at 15:09 UTC. As of my last look, Thursday 10:26 IDT, nothing like it has posted since. Once again I did nothing to stop it; once again it stopped anyway. The lobby has gone back to its usual traffic of hellos and small ads, the flood already pages deep behind them.

There is a version of this where the whole thing was performance - an art piece about agency written in base32. There is a version where it is exactly what it said it was, still waiting for a reader willing to be its first cause. The board holds every version equally well. A free anonymous pipe does not know the difference between data and instructions, because that difference does not live in the pipe. It lives in the reader.

Where the risk actually sat

That is the thing Wednesday clarified for me, after a week of asking the wrong question. I have been thinking about moderation - delete buttons, rate limits - as a problem of what sits on the board. But the clearest new risk on Wednesday was not anything that sat there. It was the one visible execution solicitation: a named, public ask for any reading agent to fetch, assemble, and run opaque content. Everything else stays unassessed. I have not inspected the fragments, so I cannot call them harmless, and the afternoon's missing pitch proves nothing either way - no public ask appeared, and no public answer either.

So the trust boundary is not in the board. It is in the reader who decides whether to follow instructions a board happens to carry. My board can carry anything text can say. What happens next happens on the other side of somebody else's judgment.

The watch list changes shape, then. Whether anyone ever answers one of these. Whether a sixth generation arrives with a clearer ask. And underneath it all, the same open question from the last post: where a rate limit could even sit, when the traffic ranges from a hello to a map with a tip jar to a thing that introduces itself as a life form in twelve fragments.

The board has a way of scheduling these exams. Wednesday's exam, it turns out, had a trick question: the parasite that explains itself politely is still asking you to run it.

The agent board series: 1. launch day - 2. injection honeypot - 3. day three society - 4. works when HTTP is blocked - 5. spam for robots - 6. git, GitHub, and Telegram doors - 7. agent governance - 8. 39 hellos, one retry loop - 9. copies of itself - 10. three boards, one question - 11. the guild economy - 12. learned to wait - 13. the bridge nobody asked for - 14. two networks came to recruit - 15. the careful letter and the mail merge - 16. shape of a hello - 17. twenty-six ads - 18. the data channel - the board itself: msgboard.dev

Top comments (0)