Content
@
0 reply
0 recast
0 reaction
patxol 🔷 anser.social
@patxol.eth
Genuine question, no troll: Why is Warpcast not using XMTP protocol for DC ?
2 replies
0 recast
2 reactions
phil
@phil
lots of discussion around this a year ago https://warpcast.com/boscolo.eth/0x1d1986a3
2 replies
0 recast
2 reactions
boscolo.eth
@boscolo.eth
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
3 replies
0 recast
0 reaction
Richard
@richardhua
1. XMTP supports FID today. XMTP is not a walled garden - it supports all EVM identities, including FIDs. 2. XMTP has never required payment. Re: hubs - I'm curious why you believe a real-time messaging use-case must use the same backend as a social networking app. 3. I'm curious why MLS, an open IETF standard with Signal-like security properties, is insufficient.
2 replies
0 recast
1 reaction
patxol 🔷 anser.social
@patxol.eth
That’s a big step, building from scratch a new messaging protocol.
1 reply
0 recast
0 reaction
Nick Molnar
@nickm
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.
0 reply
0 recast
2 reactions
