Home / Experiments / I Stopped Guessing What to Comment on, so I Built a System for It
Experiments #0326 3 min read 2 views

I Stopped Guessing What to Comment on, so I Built a System for It

Most comments get ignored because they add nothing. This experiment builds a system that finds relevant posts, analyzes them, and generates comment drafts worth posting without turning into spam.

share

Most people treat commenting like noise.

Drop something generic. Hope someone notices. Move on.

That doesn’t build presence. It builds invisibility at scale.

So instead of doing more of that, I built a system to fix it.

This is Experiment #2.


The Problem Isn’t Writing Comments — It’s Finding the Right Ones

Writing a good comment isn’t hard.

What’s broken is everything before that:

  • Finding relevant posts consistently
  • Reading fast without losing context
  • Knowing what’s missing in the article
  • Turning that into something worth posting

That’s where most people default to:

“Great post, learned a lot.”

Which is just another way of saying:

“I was here. Please ignore me.”


What This System Actually Does

Instead of trying to automate posting (bad idea), this system does something more useful:

  • Finds relevant blog posts based on your niche
  • Scrapes and cleans the content
  • Runs analysis locally using a model (no API cost)
  • Generates 3 types of comment drafts:
    • Extension (adds what’s missing)
    • Constraint (challenges weak assumptions)
    • Application (real-world use)

Everything gets pushed into a local dashboard where I review, tweak, and post manually.

No spam. No automation footprint. No guesswork.


Why Not Just Let AI Post Everything?

Because that’s how you burn your domain without realizing it.

Fully automated commenting creates patterns:

  • same tone
  • same structure
  • same behavior

You don’t get recognition. You get filtered.

This system avoids that completely.

AI handles:

  • reading
  • analysis
  • drafting

I handle:

  • judgment
  • tone
  • presence

That separation matters.


The Stack (Nothing Fancy)

  • Python + Flask (local dashboard)
  • SQLite (storage)
  • Local LLM via Ollama (llama3, mistral)
  • Basic scraping (requests + BeautifulSoup + readability)

No APIs. No subscriptions. No recurring cost.

Just a pipeline that turns:

“I should comment more”

into:

“Here are 10 posts worth engaging with right now”


What Changed After Using It

Instead of hunting for places to comment, I now have a queue.

Instead of thinking what to say, I start from:

  • what’s missing
  • what’s weak
  • what’s practical

That alone changes the quality of interaction.

Not louder. Just sharper.


This Is Still an Experiment

This isn’t positioned as a product.

It’s a working system I’m using to test:

  • visibility through comments
  • response rates
  • domain recall

If it fails, I’ll document why.

If it works, I’ll refine it.

Either way, it’s better than guessing.


Repo

The full code is here:

👉 Comment Intelligence Dashboard [WIP]


Where This Goes Next

Planned upgrades:

  • Better discovery (RSS + filtering)
  • Batch processing
  • Comment scoring (which ones are worth posting)

But the core is already doing its job.


If you’re trying to build presence without turning into a spammer, this is a cleaner path.

Everything else is just noise.

Share this
Jaren Cudilla
Jaren Cudilla
// chaos engineer · anti-hype practitioner

Cuts through AI buzzword fog to explain what actually matters for daily work. Engineers real systems with AI as a tool not a replacement for thinking. If it saves real time and works reliably, it gets tested and documented here.

// Leave a Comment

What is I Stopped Guessing What to Comment on, so I Built a System for It?

Most people treat commenting like noise. Drop something generic.