3 ms·
(Quiet founder here) Quiet creates small, closed, private IPFS networks specific to each community, so it avoids a lot of the performance problems that plague t
by holmesworcester 3y ago
(Quiet founder here) Quiet creates small, closed, private IPFS networks specific to each community, so it avoids a lot of the performance problems that plague the big global IPFS network, and is also a lot more private!
We've run real tests with hundreds of nodes on Fargate and saw message delivery times grow to just a second or two. Plus there's a lot of room for optimization because right now OrbitDB doesn't even use the gossip network for broadcasting message data--it just broadcasts DAG heads and peers have to fetch message data in a second step!
Making initial connections between peers is slow over Tor, and there are some known issues in Quiet right now when switching networks. But those aren't IPFS issues and once you're connected it's surprisingly fast.
Also, while IPFS suffers from scaling issues, the underlying gossip network (which for us is the most important part) is currently powering the Ethereum beacon chain, which has a massive number of peers (~800,000 IIRC?). So the gossip protocol library Quiet builds on is very robust. Future optimizations of Quiet will likely move the burden of moving data down the stack to the gossip protocol, and only use IPFS for "catch up" syncing and ensuring eventual consistency.