Interview with Signal President Meredith Whittaker

MobileCoin and Crypto Integration

• Multiple commenters want hard questions about Signal’s cryptocurrency integration.
• Some believed MobileCoin had been removed; others linked official support docs showing payments still present, now under a different brand.
• The rebranding and continued presence are seen by several as confidence‑reducing “cruft” that should be removed.
• A few explicitly stopped donating or using Signal when crypto was added and view it as incompatible with the nonprofit, anti‑fad narrative.

Backups, Retention, and Security Tradeoffs

• Debate over whether lack of easy backups is a feature (reduced attack surface) or a usability flaw.
• Several note that strong, usable backup encryption is an unsolved problem; typical options lead to weak passphrases or risky server‑side protection (e.g., SGX), which some are glad Signal avoids.
• Others point out that Android and Desktop already have backup mechanisms, and third‑party tools can read them, making the “no backups” stance inconsistent, especially with iOS lacking parity.
• Some argue that serious users can and do preserve history via desktop clients or CLI tools anyway, so defaults and UX matter more than theoretical policy.

Multi‑Device Support and Alternative Clients

• Frustration that one account cannot be used on multiple phones/tablets; only phone + desktop is supported.
• Third‑party forks like Molly are cited as adding features such as multi‑phone use, though not across all platforms.
• Some users move to other ecosystems (e.g., XMPP/Snikket, Matrix/Beeper) to consolidate messaging and get multi‑device support.

Trust, Governance, and Compensation

• Several praise the nonprofit structure and relatively modest executive compensation, seeing it as aligned with mission.
• Others debate whether paying fewer, highly compensated engineers vs more moderately paid ones is better, emphasizing that top engineers can be vastly more productive and that pay can reduce corruption risks.

Adoption, Funding, and User Experience

• Many report growing use of Signal in their circles, including older, nontechnical family members, especially for cross‑platform messaging and video.
• Some still prefer Matrix/Beeper for unified messaging despite acknowledging Signal’s superior polish.
• There is curiosity and confusion about where Signal’s reported tens of millions in annual funding come from.

China, Blocking, and Threat Models

• Mixed reports on whether Signal works in China: some used it successfully pre‑COVID; others say it has been blocked for years, with SMS activations and App Store presence removed.
• Censorship‑resistant routing is mentioned, but how well it currently works is unclear.
• One line of discussion rejects the claim that continued operation (when it occurred) implies a government backdoor, arguing that low user counts or signup friction are simpler explanations.
• Even without backdoors, participants note that traffic metadata (timing, size) can still be used for correlation by powerful adversaries.

Open Source, Self‑Hosting, and Anonymity

• Some explore running their own Signal‑protocol servers/clients using libsignal, but note tradeoffs:
  • Loss of anonymity due to standing out from mainstream traffic.
  • Risky protocol tweaks and maintenance burden.
  • Limited gains beyond control over contact‑discovery metadata.

Media Framing, Hype, and Criticism

• A subset finds the article hagiographic and questions why Signal is treated as “the one true secure messenger,” suggesting social pressure and possible “shilling.”
• Others highlight prior interviews and transparency reports as building trust rather than blind hero worship.

Nonprofit vs For‑Profit, AI and Fads

• Commenters react positively to the argument that a nonprofit avoids board‑driven pressure to chase profit‑oriented “AI strategy” fads.
• Critics respond that nonprofits can still chase fads (e.g., crypto), depending on their boards.

Cloud Concentration and Infrastructure Risk

• A widely approved point is that heavy reliance on a few cloud providers is dangerous; one recent incident shows how flaws at a single security vendor plus a cloud giant can disrupt large portions of critical infrastructure.