# Can RSS be a social network (Dave Winer) > [!question] Lingering Questions > - Does the WordPress IndieWeb plugin stack already satisfy Winer's "textcasting" requirements, or is there a real gap? > - How does the textcasting RSS+WebSockets stack compare feature-by-feature against ActivityPub? > [!tip] Article Ideas > - "Text should be a format, not a platform" — the MP3 analogy as a hook for an IndieWeb/interop piece. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Perm · Markdown won because it solved the format lock-in problem, not for syntax]] — same lock-in-vs-format logic, different medium > - [[3. Resources/Permanent Notes/Portability Is Proven by a Second Implementer Not by Design Intent]] — the interop claim here needs this test applied before it's trusted > - [[3. Resources/Permanent Notes/Building on a Platform You Don't Control Is Renting Not Owning]] — the platform-lock-in half of the same argument > [!quote] Vocabulary > - *Textcasting* — Winer's proposed spec for treating short-form text posts as a portable, syndicatable format like RSS treats articles ## Metadata - Source: [[3. Resources/Readwise/Full Document Contents/Articles/Can RSS be a social network]] - Author: Dave Winer (scripting.com) - URL: http://scripting.com/2026/07/09/152001.html?title=canRssBeASocialNetwork ## Author's thesis RSS-style syndication could function as a genuinely open social network if every part of the stack — client, format, transport — were interoperable and replaceable, but the reason it doesn't today is commercial incentive, not a missing technical piece. ## Key arguments 1. The design principle for an open social network: every part replaceable, interop everywhere — no single vendor lock-in point. 2. Text posts should be a universal, portable format the way MP3 is for audio, not something trapped inside a platform's length caps and single-author model. 3. The incompatibility between today's big networks is a business choice, not a technical limitation. ## Claim atoms ### Open social networks require replaceable, interoperable parts > [!quote] ID:rw_01kx4tefgvgn1v128f2987fn18 > The right way, the way the web would do social networking: Every part is replaceable. Interop everywhere. Where/why: near the close of the post, the summarizing design principle — the core anti-lock-in thesis. #xref #aphorisms ### Text should be a universal format like MP3 > [!quote] ID:rw_01kx4tefgvgn1v128f2987fn18 > We'd think of text the same way you think of MP3. It just should work everywhere. Where/why: mid-post analogy attacking platform-imposed limits (length caps, single-author); reframes portability as a solved-elsewhere problem. #xref ### Incompatibility between networks is commercially motivated > [!quote] ID:rw_01kx4tefgvgn1v128f2987fn18 > The fact that our text can't go everywhere is because the big networks don't want to be compatible with each other. Bad for business. Where/why: identifies the barrier as economic incentive, not technical limitation — the crux claim for anyone arguing federation policy. #xref #articleseed ## Permanent candidates - **New**: [[3. Resources/Permanent Notes/A Network Is Open Only When Its Parts Are Independently Replaceable]] — built from the H1 atom above; checked against existing lock-in notes first (see Cross Reference) and found distinct enough to stand as its own claim about network-level (not format-level) openness. ## Processing checklist - [ ] Read the textcasting spec and note gaps vs. IndieWeb (https://textcasting.org/) - [ ] Compare textcasting's RSS+WebSockets stack against ActivityPub feature-by-feature - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Open Source Governance MOC]] ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — interoperability-as-governance-property is the same lever this MOC tracks for code - [[3. Resources/Permanent Notes/A Network Is Open Only When Its Parts Are Independently Replaceable]] — evidence-for; the Permanent claim distilled from this source - [[3. Resources/Permanent Notes/Perm · Markdown won because it solved the format lock-in problem, not for syntax]] — sibling claim, same lock-in logic applied to a document format instead of a network