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

On the other hand, I could also ask why xmtp does not provide better integration with Farcaster. For example a way to use XMTP with my Farcaster custody wallet (can I?). Or populate my contacts and filter conversations using my Farcaster social graph.

Messaging for web3 people. Built with @xmtp https://converse.xyz/ /converse

For example, why doesn't @converseapp support sign-in with Farcaster? Is it a protocol design limitation? What would it take?

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za

If we could use xmtp with sign-in with farcaster, and automatically get our profile and address book populated, and spam filtering using my Farcaster social graph, it would be cool.

A real "opportunity for a client".

This is what I meant. Some changes at the protocol level to support FC integration. And then, it's up to the clients.

xmtp is the protocol and they have many clients so it's not as simple as xmtp implementing all these features

you can create an xmtp account with your farcaster custody wallet, however a more interesting integration would be if the protocol let you create xmtp signers using farcaster signers (eddsa) instead of just an ethereum wallet