/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Substack wants to be seen as a pure infrastructure provider, akin to Cloudflare, but a platform can't claim to be simple software when it recommends content

Some thoughts on platforms and Nazis  —  Most days, this column looks at controversies unfolding on other tech platforms.

Platformer Casey Newton

Context & Ripple Effects

Substack’s defense of permissive content rules had already been challenged after reporting found Nazi and white-supremacist newsletters on the service and co-founder Hamish McKenzie publicly resisted calls for their removal. This piece identifies a tension in that defense: recommendation is an editorially consequential product choice, not merely neutral hosting.

That distinction matters because Substack’s effort to avoid value judgments sits alongside a product designed to help readers discover publications. Its claimed infrastructure analogy is therefore tested by the role its interfaces play in distributing attention.

First-order effects

  • Substack’s recommendation features become central to scrutiny of its Nazi-content policy: the company is accountable not only for what it hosts, but for what it actively surfaces to readers.
  • Authors and readers evaluating the service have a clearer basis to distinguish passive publication tools from product decisions that can amplify particular newsletters.

Second-order effects

  • Pressure on Substack shifts from a binary moderation question toward governance of ranking, discovery, and promotional interfaces—the mechanisms through which hosted material gains reach.
  • A later partial removal policy would not resolve that broader issue if extremist publications can still be discovered or recommended through product design.

Third-order effects

  • If this framing spreads, platforms will find it harder to claim infrastructure-style neutrality while operating recommendation systems; distribution choices may become the practical test of platform responsibility.
  • The likely durable divide is between genuinely user-directed tools and services that curate attention at scale, with trust depending on whether governance follows that distinction.

The trend: Content platforms are increasingly being judged by their distribution and recommendation systems, not only by their stated rules for hosted material.

Discussion

  • @wiczipedia Nina Jankowicz on threads
    I think @crumbler and @reporterzoe just might crack them. https://open.substack.com/...
  • @dangillmor@mastodon.social Dan Gillmor on mastodon
    With respect to @caseynewton and his colleagues at Platformer, it's long past time to fish or cut bait with Substack.  —  The platform isn't at a crossroads.  It has made entirely clear that helping Nazis monetize their extremism is part of the business model, and that while even…
  • @cooperlund.bsky.social Cooper Lund on bluesky
    There's a bigger problem with Substack's (bullshit) claim that it's a “pure infrastructure” provider - they gave people a bunch of money to post on their platform!  You can't put the editorial toothpaste back in the tube after you've done that one! [embedded post]
  • @anildash.com Anil Dash on bluesky
    there's no such thing as a “pure infrastructure provider” aaaactually [embedded post]