Genuine question, no troll:
Why is Warpcast not using XMTP protocol for DC ?

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

If you are considering 1, why not just use XMTP?

Instead of a Warpcast-only DC functionality, I'd rather see those 6-12 months spent adding an open source DC capability to Hubs, so all FC clients can use it.

lots of discussion around this a year ago

🟪building /f4r https://f4r.xyz | prev. Ledger

lots of discussion around this a year ago 

https://warpcast.com/boscolo.eth/0x1d1986a3

With the benefit of hindsight, this was the right decision.

DC/GC in Farcaster should:
1️⃣ Be based on FIDs & FC KeyStore. (XMTP has its own ID layer.)
2️⃣ Use Hubs for message delivery. (XMTP servers require additional payment.)
3️⃣ Use

Building /bright-moments - minting onchain art IRL | /purple #15 | FID 129 #magikarp

With the benefit of hindsight, this was the right decision.

DC/GC in Farcaster should:
1️⃣ Be based on FIDs & FC KeyStore. (XMTP has its own ID layer.)
2️⃣ Use Hubs for message delivery. (XMTP servers require additional payment.)
3️⃣ Use https://github.com/farcasterxyz/protocol/discussions/99

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

XMTP's identity layer is super lightweight so it can be composable with other identity providers like ENS and FID.

@cassie is wicked smart. And very generously spent some time with our team last year to walk us through FIP-99. I sure hope FC ends up using it, since the privacy is 1,000X better than Warpcast today.