>A smart designer of a Decentralized application could see not storing data in a centralized storage, as an advantage because it lets them side step all of these problems.
This doesn't sidestep the core problem of curation, though. It depends on the nature of the application, but just looking at ones that involve displaying user-submitted publicly: if you don't have a frontend with some manner of filtering and moderation, the app will quickly be overwhelmed with a flood of spam and illicit activity (ranging from copyright infringement to child abuse).
Things like IPFS work great for decentralized content storage if you don't need to provide any sort of curation or frontend. But if you do, you'll quickly find yourself running what reduces to a centralized platform. Or if you're providing a federated service of some kind, then your users will be the ones who find themselves in that situation.
This doesn't sidestep the core problem of curation, though. It depends on the nature of the application, but just looking at ones that involve displaying user-submitted publicly: if you don't have a frontend with some manner of filtering and moderation, the app will quickly be overwhelmed with a flood of spam and illicit activity (ranging from copyright infringement to child abuse).
Things like IPFS work great for decentralized content storage if you don't need to provide any sort of curation or frontend. But if you do, you'll quickly find yourself running what reduces to a centralized platform. Or if you're providing a federated service of some kind, then your users will be the ones who find themselves in that situation.