HN Debrief

Substack writers, you need a website

  • Media
  • Open Web
  • Startups
  • Developer Tools

The post’s core argument is straightforward: Substack is useful, but writers should not confuse a rented publishing platform with owning their presence on the web. A personal site gives you a stable archive, design control, and a way out if the platform changes terms, breaks discovery, or turns into the next Medium. That framing landed well, but most of the useful discussion sharpened it into a more practical rule: keep your own domain and the original copy of your work, then use Substack for what it is actually good at, which is email delivery, payments, and audience growth.

If you publish on a platform, keep your own domain and your original content under your control, then treat Substack or similar services as distribution. If audience growth or paid subscriptions matter, assume you will need both ownership and a push channel, not just a static site.

Discussion mood

Mostly favorable to the article’s core warning about ownership and lock-in, but pragmatic rather than ideological. People were willing to criticize Substack’s creep toward enclosure, ugly reader experience, and moderation choices, yet many still said it solves the hard parts of writing online better than a standalone site does today.

Key insights

  1. 01

    Canonical site plus syndicated Substack works

    Keeping your own site as the source of truth turns the platform question from a loyalty test into an operational choice. Several long-time bloggers described publishing first on their own domain, then copying the same work into Substack for email and discovery. That preserves URLs, archives, and formatting while still using Substack where it has leverage. It also avoids repeating the Medium mistake of letting a third party become the only home for years of work.

    If you are already on Substack, do not migrate everything first. Start by making your own domain the canonical archive for all new posts and syndicate outward from there.

      Attribution:
    • simonw #1
    • jmmv #1
    • millipede #1
    • wxw #1
  2. 02

    The real product is email ops and payments

    The expensive part of independent publishing is not serving pages. It is deliverability, bounces, unsubscribes, billing, and tax handling. People who could plainly self-host still chose Substack because those chores become real work at scale, and because a Merchant of Record removes painful compliance overhead. That reframes the platform fee as buying operations, not just templates and hosting.

    Before replacing Substack, price the full stack you would need to run yourself, including compliance and deliverability. A cheap blog host is not a substitute for a newsletter business.

      Attribution:
    • simonw #1 #2
    • drdexebtjl #1
    • t-writescode #1 #2
  3. 03

    Exportable emails are not the whole story

    Subscriber export sounds like a clean escape hatch, but the sticky parts of a platform often live outside the CSV. Commenters flagged that Substack Notes is not exportable, some app-based subscriptions route through Apple or Google, and product choices increasingly steer readers into the app. That means your audience graph and conversion funnel can become trapped even if your mailing list is nominally portable.

    Audit which parts of your audience relationship are actually portable. If growth depends on Notes, app subscriptions, or in-platform discovery, assume a future migration will be messier than an email export implies.

      Attribution:
    • rsingel #1
    • Forgeties79 #1
    • nicbou #1
  4. 04

    Substack discovery is uneven, not universal

    Claims about Substack’s network effect split by publisher size and niche. Some writers reported substantial subscriber growth and said most new signups now come from Substack mechanisms. Others said internal discovery barely moved the needle and nearly all readers still came from external links. The practical read is that Substack’s recommendation engine behaves more like an amplifier for momentum than a guaranteed audience bootstrapper.

    Do not choose Substack on the assumption that the platform will discover readers for you. Test whether its internal growth channels work for your niche before you make it your primary home.

      Attribution:
    • peteforde #1
    • InsideOutSanta #1
    • simonw #1
    • div3rs3 #1
  5. 05

    Open alternatives still lack the network moat

    Ghost, Leaflet, Offprint, Pckt, and AT Protocol-based publishing all surfaced as credible ways to avoid lock-in. What none of them yet match is the concentration of readers, recommendations, and payment behavior that makes Substack attractive to writers in the first place. The tooling problem is largely solved. The audience aggregation problem is not.

    If you pick an open alternative, plan to bring your own distribution. Better infrastructure does not automatically recreate the audience economics of a closed platform.

      Attribution:
    • Uehreka #1
    • ValdikSS #1
    • Chaseraph #1
    • schlagetown #1

Against the grain

  1. 01

    For many writers, a website is dead weight

    If your goal is readers rather than sovereignty, a standalone site can be a beautifully maintained empty room. Several people said independent blogs now get negligible traffic, search is weaker, social platforms suppress links, and subscription conversion from a cold website is terrible. From that angle, insisting on a personal site first can become advice that feels principled but ignores how people actually find writing now.

    If you are starting from zero and need audience growth fast, optimize for distribution first and ownership second. You can add a canonical site later once the writing has found real readers.

      Attribution:
    • skippyfish #1
    • tombert #1
    • f311a #1
  2. 02

    Writing does not need an audience business

    A smaller but credible pushback rejected the premise that every writer should optimize for reach, subscribers, or monetization. Technical bloggers and hobbyists said they write to document solutions, think clearly, or make something for its own sake. For that use case, searchability and permanence matter more than funnel metrics, and in some cases no platform at all is the right answer.

    Decide whether you are building a media business or keeping a public notebook. Those are different products and they should lead you to different publishing choices.

      Attribution:
    • skippyfish #1
    • ryukoposting #1
    • ValdikSS #1
  3. 03

    A platform hostname may outlive your domain

    One commenter flipped the ownership argument by pointing out that personal domains expire when the owner stops paying. A hosted URL might actually preserve writing longer than a self-managed domain if the goal is posthumous survival rather than present-day control. The Internet Archive was offered as a partial fix, but archived URLs are not the same thing as a living site.

    If long-term preservation matters, add an archival plan. Ownership today does not guarantee accessibility decades from now.

      Attribution:
    • Stratoscope #1 #2

In plain english

AT Protocol
Authenticated Transfer Protocol, an open social networking protocol used by services like Bluesky to let different apps interoperate on shared social data.
Ghost
An open source publishing platform focused on blogs, newsletters, and memberships.
Merchant of Record
A company that legally handles payment collection, taxes, compliance, and related financial responsibilities on behalf of a seller.
POSSE
Publish on your Own Site, Syndicate Elsewhere, an IndieWeb practice where you keep the original post on your site and repost copies or links on other platforms.

Reference links

Publishing models and migration guides

Open publishing alternatives

  • Leaflet
    AT Protocol-based publishing app proposed as an open alternative to Substack or Ghost.
  • Standard.site
    Publishing interoperability standard intended to make content discoverable across apps and sites.
  • Standard Reader
    Reader app example built on the Standard.site ecosystem.
  • WriteFreely
    Mentioned for comparison with Leaflet as another open publishing tool.

Broader critiques of platform dependence

Examples and supporting tools