I root for the Warpcast team. But I would appreciate an updated explanation why @xmtp is not our default IM/GC protocol (with all the nice things a deep integration with Farcaster could add).

Honest question, and I know very little about the XMTP design, so the answer may be very simple and I'm just missing it.

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

What problem does it solve for us right now?

Decentralized IM and GC, with a wider reach than FC. Also a dedicated team working on what currently is just a Warpcast feature, with some (limited afaik, my be wrong) REST APIs.

Because XMTP groups are end-to-end encrypted and authenticated using MLS, the best way to interface with the network is to use one of the platform-specific client libraries. Here’s React Native: 

https://github.com/xmtp/xmtp-react-native/tree/beta

You can use gRPC if you only need basic publish/subscribe/query operations:

Because XMTP groups are end-to-end encrypted and authenticated using MLS, the best way to interface with the network is to use one of the platform-specific client libraries. Here’s React Native: 

https://github.com/xmtp/xmtp-react-native/tree/beta

You can use gRPC if you only need basic publish/subscribe/query operations:

https://github.com/xmtp/xmtp-node-js-tools