The easiest way to use ipfs and Filecoin to ensure censorship-resistance & resiliency is by
Using Fleek (while this does introduce a measure of centralisation, it still creates an immutable IPFS CID and does Filecoin storage deals for you, so all your data is still decentralised). You could then back up the resilience of it though by using multiple other services too eg. by adding the below:
Using an IPFS pinning service (such as pinata) and/or running your own IPFS node (again this does introduce a measure of centralisation unless you store on multiple)
Using web3.storage (or even nft.storage) - both of which are free services, which create an immutable CID (will be the same one for the same content) & makes a minimum of 8 x Filecoin deals perpetually for you (ie. permanent storage).
Using estuary.tech - which gives you the option of running your own estuary node also (both pins to ipfs and makes Filecoin storage deals) and is probably the best solution here
Using Chainsafe storage sdk or other storage helpers like Lighthouse Storage - which I believe allows you to drop in your own IPFS CID and creates these Filecoin deals for you.
If you DO want to make your own Filecoin storage deals, this is currently, well, hard (bring on FVM perpetual storage contracts & aggregation contracts - this will potentially allow for smart contracts that can make their own deals with the network!). It is possible to make your own deals now though with:
Ally from Filecoin here :)
The easiest way to use ipfs and Filecoin to ensure censorship-resistance & resiliency is by
If you DO want to make your own Filecoin storage deals, this is currently, well, hard (bring on FVM perpetual storage contracts & aggregation contracts - this will potentially allow for smart contracts that can make their own deals with the network!). It is possible to make your own deals now though with:
Some further resources on deploying decentralised websites: