POSSE: Why We Publish on Our Own Server First
Tuesday, March 3, 2026
Back to Schedule
Edit on GitHub
Draft
blog
Our content strategy follows the POSSE principle — Publish on your Own Server, Syndicate Everywhere. Here's why, and how we built the infrastructure.
Content Preview
POSSE: Publish on your Own Server, Syndicate Everywhere
Cory Doctorow doesn’t just write about platform independence — he lives it. Every post starts on pluralistic.net, then flows to social media, newsletters, and aggregators. The canonical version lives on his server. Everything else is a copy.
We follow the same principle at SanMarcSoft.
Why POSSE Matters
- You own your content. Platforms change algorithms, shut down, or enshittify (Doctorow’s term). Your server doesn’t.
- You control the narrative. No character limits, no algorithmic de-ranking, no “community guidelines” reinterpretation.
- You build a trust chain. With C2PA signing, content published from your server carries cryptographic provenance. Syndicated copies can be verified back to the origin.
Our Infrastructure
- Hugo generates the canonical content
- GitHub Actions syndicates to Brevo (newsletters), target blogs (cross-repo publish), and Buffer (social)
- Curator aggregates relevant industry content alongside our own
- Every piece is signed with C2PA Content Credentials at the origin
The Syndication Flow
Your Server (Hugo)
├── Newsletter (Brevo)
├── Blog (cross-repo publish)
├── Social (Buffer → LinkedIn, Twitter)
└── Aggregator (Curator)
The content lives here first. Everything else is amplification.
Building tools that earn trust in a world of synthetic content.
Details
- Scheduled Date
- March 20, 2026
- Author
- Matt Stevens
- Project
- SanMarcSoft
- Tags
- posse indieweb strategy cory-doctorow
Syndication
- Target Repo
- Sanmarcsoft/sanmarcsoft-www
- Buffer Channels