<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>independent media on Publishing House</title>
    <link>https://publishinghouse.org/tags/independent-media/</link>
    <description>Recent content in independent media on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/independent-media/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Indie Publisher&#39;s Case for Owning Your Infrastructure</title>
      <link>https://publishinghouse.org/the-indie-publishers-case-for-owning-your-infrastructure/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/the-indie-publishers-case-for-owning-your-infrastructure/</guid>
      <description>Every few years, a platform that indie publishers relied on changes the rules. Algorithm changes cut organic reach. Monetization programs introduce new requirements or reduce payouts. Accounts get suspended without clear appeal paths. The terms shift in ways that favor the platform over the publisher.
This is not a new dynamic. It predates the internet. But the specific form it takes now — where a significant portion of an independent publisher&amp;rsquo;s audience, revenue, and distribution lives on infrastructure controlled by companies whose interests regularly diverge from the publishers they host — is worth examining directly.</description>
    </item>
    
  </channel>
</rss>
