IPFS Deployment for Censorship Resistance

Venice is a private, permission-less AI. What about making it censorship resistant?

Deploying the Venice Front-End to IPFS would enable the app to resist censorship (e.g., bypass corporate blocking) and enhance its resilience and accessibility.

It would make the Front-End decentralized, i.e., accessible through any node.

However, the Back-End would still be blocked if the domain venice.ai is on a blacklist by a corporation wanting to restrict its employees, for example.

Something else, such as relying on smart contracts, libp2p, or other solutions, would then need to be figured out to make the app fully work in a censorship-resistant way.

In my opinion, implementing a censorship-resistant solution would align with Venice's private and permission-less AI principles, and potentially aim towards a fully decentralized and web3-friendly platform.