← Back to archive

Why your content should live on your own site

12 June 2026 · 2 views · 0 likes · 0 reposts · 184 blog views

AI Content Indie Hacking Node.js SEO SQLite

@levelsio raised a pretty important point when he vibe-coded his blog.

Social networks are great for distribution but they should not be the source of truth for your content.

You write ideas for years, publish them on X, and slowly lose control over the archive. Old posts are poorly indexed, hard to find, eventually buried under the feed, and - more importantly - you can't use them to train your own local AI models.

So I got rid of my old WordPress blog where I rarely wrote, migrated the old posts, mixed them with my X content in a single place. Basically it's the vibe-coded open-source project that combines everything into a personal content aggregator - something like Hacker News for your own writing.

Each post gets its own SEO-friendly page, tags, related posts, view counters, a permanent URL on your domain.

The setup is intentionally super simple:

  • SQLite, one file
  • Vanilla Node + TypeScript, no build step
  • SEO built in (JSON-LD, sitemap, RSS)
  • Full-text search
  • Highly customizable
  • Runs on a tiny @Hetzner_Online VPS

Your content should belong to you.

Source code 👇

Github: github.com/desunit/EchoPo… Live demo and my blog: desunit.com/blog

View on X

Github: github.com/desunit/EchoPo… Live demo and my blog: desunit.com/blog

View on X

Why your content should live on your own site

Originally posted on X

PS: I'm pretty active on 𝕏 if you'd like to follow along

Related posts

Archive

2026

2025

2024

2018