the idea is that if there's 100 providers eventually, and only 1 needs to not censor you to get your content, then it's unlikely you will be censored
we plan on adding IPFS webrtc and webtransport at some point, to reduce the need and load on the ipfs gateways, and whatever new that comes out that can help the browser/mobile clients. For example https://iroh.computer/ seems promising
the desktop client is fully P2P, it bundles an IPFS node, and the only requests it makes are through the IPFS node. (technically it makes one request to github for default communities, but we will remove that at some point). Also if your community or username uses a human readable name (optional), then you need to resolve that name somehow, we can technically support any name system anyone makes, and that might or might not be P2P.
the idea is that if there's 100 providers eventually, and only 1 needs to not censor you to get your content, then it's unlikely you will be censored
we plan on adding IPFS webrtc and webtransport at some point, to reduce the need and load on the ipfs gateways, and whatever new that comes out that can help the browser/mobile clients. For example https://iroh.computer/ seems promising
the desktop client is fully P2P, it bundles an IPFS node, and the only requests it makes are through the IPFS node. (technically it makes one request to github for default communities, but we will remove that at some point). Also if your community or username uses a human readable name (optional), then you need to resolve that name somehow, we can technically support any name system anyone makes, and that might or might not be P2P.