Although I understand the needs-to-be-pinned limitation makes sense for generic data, I feel like it breaks down the use case of hosting a static website where you don't wanna worry about availability.

Pinning services are more expensive than cloud storage.

Plus, the great idea of no central authority of IPFS makes less sense for purposely exposed public content (website). Even though AWS controls my data, every user accessing my site has every bit of data from it. The authority controls the serving but hasn't real power on the data itself which is rebuildable from code and publishable somewhere else at anytime.

FileCoin seems to solve this case if I understand correctly, but IPFS on itself, at least for static website hosting doesn't.

Any counter opinion?