Product 28 Sep 2026
Why we built Slop Cannon
It scans for possible stories. Its real job is knowing when to leave them alone.

The name is a joke. The problem isn’t.
If you ask a content tool to post more often, it will find a way. It can turn a flimsy observation into five confident paragraphs, or give you a “hot take” whose only heat comes from punctuation. The output looks ready. The reader gets nothing.
Slop Cannon starts with a sweep of posts in your niche and, if you choose, recent notes from your own idea sources. It looks for something worth discussing, then tries to check whether there is enough substance to build on. A candidate can become a standalone post, a quote post that makes sense with the source attached, or no draft at all. The drafts go to your review queue. You decide what to approve, schedule, edit, or send.
That distinction between a post and a quote matters. Sometimes the interesting thing is somebody else’s report or observation. Pretending your commentary stands on its own strips away the context the reader needs. A good quote post should add a view, not merely point at the source. A standalone post has to earn its independence.
The harder gate is quality. Did the source actually say what the draft claims? Is there a specific reason the reader should care? Is there a view that sounds like you, rather than a generic “this changes everything”? We are making that filter stricter, and it has exposed another problem: on a recent run the sweep scanned more than 150 posts and saved nothing. Some rejected material was genuinely weak. We still need to verify that worthwhile stories can get through. The next scheduled live sweeps will tell us more than a green build can.
I would rather have an empty review queue than one full of invented confidence. But an empty queue every time is not a useful product either. The goal is a smaller set of drafts you can defend, with a clear reason each one is there.
If Slop Cannon earns its name, it will be because it catches the slop before you see it.