Content
@
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
For people who want DCs on web, do you prefer: 1. No Encryption - would ship this month, encryption added later, other fc clients could integrate next year 2. Encryption - takes another 6-12 months b/c blocked on Google Chrome passkeys support
79 replies
12 recasts
102 reactions
boscolo.eth
@boscolo.eth
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.
1 reply
1 recast
3 reactions
Varun Srinivasan
@v
On using XMTP instead of building a simple DC service that works across all fc clients - lots of risk, no gain. Might change in the future, but doesn't make sense today.
2 replies
1 recast
2 reactions
Dean Pierce 👨💻🌎🌍
@deanpierce.eth
What's the risk? XMTP is fully e2ee right now, and several apps seem to have added in XMTP support without much issue. Lens, Coinbase, Converse, etc. It's becoming the standard web3 messaging platform. Why is there any hesitation at all? Open standards are good, and should be embraced for a healthy ecosystem.
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
XMTP is working towards secure e2ee and decentralization. But neither of those are true today for any reasonable definitions of those terms. I wouldn't call something an open standard if there is one server controlled by a single party that can take the whole thing down.
2 replies
0 recast
1 reaction
