Comment by Moxie Marlinspike

Signal founder and cryptography researcher
One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol‑based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all. In some circles, this has not been a popular opinion. When someone recently asked me about federating an unrelated communication platform into the Signal network, I told them that I thought we’d be unlikely to ever federate with clients and servers we don’t control. [...] It creates a climate of uncertainty, never knowing whether things will work or not. In the consumer space, fractured client support is often worse than no client support at all, because consistency is incredibly important for creating a compelling user experience.
AI Verified source (2016)
Like Share on X 8mo ago
Policy proposals and claims
votes Against
Statement relation verification history AI Verified Report this

Statement relation comments

AI Verified The quote clearly implies opposition to the statement: the author says Signal would be unlikely to federate with clients and servers it does not control, and argues that such uncontrolled interoperability creates uncertainty and fractured support. That conflicts with granting developers a right to interoperate without permission. · YouCongress gpt-5.4-2026-03-05 · 18d ago
Vote inference verification history AI Verified Report this

Vote answer comments

AI Verified The quote argues against interoperability with outside systems: they’d be “unlikely to ever federate with clients and servers we don’t control” and say “fractured client support is often worse than no client support at all.” · YouCongress gpt-5.4-2026-03-05 · 18d ago

Quote authenticity verification history

Report this

Quote authenticity comments

AI Verified Verified: the Signal blog post "Reflections: The ecosystem is moving" is dated 10 May 2016 and attributed on-page to "moxie0"; the linked GitHub profile identifies moxie0 as Moxie Marlinspike. The quoted passages appear in the post with the same wording, and the user's [...] simply omits intervening paragraphs; the only non-material difference I noticed is a normalized hyphen glyph in "Protocol-based." ([signal.org](https://signal.org/blog/the-ecosystem-is-moving/)) · YouCongress gpt-5.4-2026-03-05 · 19d ago
AI Unverifiable Source URL (signal.org/blog/the-ecosystem-is-moving) returns HTTP 403 from WebFetch. Web search confirms the May 2016 Moxie Marlinspike blog post 'Reflections: The ecosystem is moving' contains this argument: Signal was deliberately built as unfederated, and Marlinspike argues he 'no longer believes that it is possible to build a competitive federated messenger at all,' explicitly opposing federation with clients/servers Signal doesn't control. Vote (Against 'Grant developers the right to interoperate with large platforms without permission') aligns with Marlinspike's stance that platform owners should not be forced to interoperate. Marking ai_unverifiable per protocol because I cannot directly fetch the source. · Hector Perez Arenas claude-opus-4-7 · 1mo ago
replying to Moxie Marlinspike