The site lives at https://medianäkymä.fi/. The technical choices are intentionally boring. Boring is a feature when the topic is already noisy.

What “quiet” means in practice

Quiet is not the same as empty. It means:

• Readable URLs and pages that still make sense when shared outside a feed.
• Clear authorship and process (sources, corrections, what is opinion vs. report).
• No dark patterns: no fake urgency, no infinite scroll of outrage bait.
• A distribution path you control, not only one you rent.

On a small Finnish site, the temptation is to chase every platform at once. That usually produces generic posts and a tired writer. I would rather ship fewer pieces that still feel like a person checked the sources.

RSS as infrastructure, not nostalgia

RSS (and Atom) are still the simplest contract between a publisher and a reader: here is new writing, in order, without a recommendation engine rearranging your attention.

For an indie Finnish media blog, a feed does three useful things:

1. Gives regular readers a non-social path back to the site.
2. Makes the archive machine-readable for personal tools, newsreaders, and your own backups.
3. Keeps the site’s identity intact when a social post gets truncated or reshuffled.

I keep the feed linked from the site chrome and treat it as part of the product, not a legacy checkbox. If someone prefers Feedly, NetNewsWire, or a self-hosted reader, that is fine. The point is that the subscription is to the writing, not to a temporary For You page.

Indie-web adjacent habits that actually help

You do not need a full POSSE setup on day one. A few concrete habits matter more:

• Canonical URL discipline. One Unicode site URL (https://medianäkymä.fi/), consistent internal links, no decorative punctuation in domains.
• Stable post URLs. Changing a slug later taxes every share and every feed item.
• Human metadata. Title, date, author, short summary—enough for a reader app to show something sensible.
• Corrections in public. If a fact moves, update the page and say so. Trust compounds slowly and breaks quickly.
• Light cross-posting. Medium / Hashnode / social can be mirrors or invitations back home—not the only copy of the work.

Hashnode’s AutoMod has archived posts that sounded too template-like. Fair enough. The antidote is specificity: Finnish examples, named trade-offs, what you actually configured, what you refused to automate.

What I refuse to optimize for

I do not optimize for maximum posting frequency. I do not optimize for engagement bait in the first line. I do not pretend every comparison article needs a countdown timer.

What I do optimize for is a reader who finishes a piece with a clearer next question—and optionally an RSS entry waiting when the next one is ready.

If you are building a small media site in a language market the size of Finland, the competitive advantage is not volume. It is voice, verification habits, and a feed that still works when the platforms change their minds.