# A Challenger Can Invite The Incumbent To Connect Not Compete ## Claim A new open protocol can position itself to strengthen rather than threaten an incumbent platform, by explicitly inviting the incumbent to connect inward instead of building a competing walled garden. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the challenger removes a specific limitation the incumbent already lacks — here, character limits — making the incumbent a natural, low-friction fit rather than a rival. - Describes a stated hope and strategic framing, not a completed integration: Winer states he "expects" WordPress will connect, with no confirmed roadmap or commitment from WordPress itself. - Doesn't establish that incumbents actually respond to this kind of invitation more often than they ignore it — that's an open, testable question this source doesn't answer. ## Evidence Winer, explaining rss.chat's relationship to his earlier related project WordLand ("designed to work with WordPress"): "This is a similar idea but without WordPress, entirely based on feeds and APIs." He states a preference for WordPress to connect into the new network rather than the reverse, reasoning that platforms imposing character limits "will have to relax their limits before it makes sense to connect here" — while WordPress, having no such limit, faces no such barrier. ## Links - [[Commons & Community Governance MOC]] — a commons-building posture toward an incumbent, rather than a displacement one - [[3. Resources/Permanent Notes/Building on a Platform You Don't Control Is Renting Not Owning]] — because contrasts; that note treats platform dependency as a risk to avoid, this one describes a builder deliberately avoiding that dependency by design, then inviting the platform in on his own terms. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; positioning a new protocol as complementary rather than competitive is a governance and adoption strategy question for open ecosystems. ## Tests / falsifiers - Watch whether WordPress (or any WordPress-adjacent project) actually builds a connector to rss.chat within a defined window — Winer's stated expectation would be falsified by continued non-adoption. - Compare against other challenger-protocol cases: does an explicit "please connect to us" framing correlate with actual incumbent adoption, or does it function mainly as goodwill signaling with no adoption effect? ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/demo.rss.chat]] — Dave Winer's reply post (id=29) explaining rss.chat's positioning relative to WordPress and WordLand.