>, but at least we don't have to subject the consumers of our frontend to it unless they opt in.
Right... but if your project gains huge awareness (or "notoriety" depending on perspective), someone else can replicate your work and show the bad bytes. (Because the urls are still there in the blockchain.) Unless I'm not understanding the architecture, the project would have escaped your ability to control it.
I think that's fine. There are really two parts: The part which stores the data (the Ethereum blockchain) and the presentation layer (https://thousandetherhomepage.com/).
There's nothing we can do about the data that ultimately ends up on the Ethereum blockchain.
But we do control the presentation layer (the domain, the frontend). We're going to do our best to do The Right Thing within the confines of what we can control.
If someone else buys another domain (eviletherhomepage.com) and renders a bunch of illegal content on it, I would argue that's on them.
Right... but if your project gains huge awareness (or "notoriety" depending on perspective), someone else can replicate your work and show the bad bytes. (Because the urls are still there in the blockchain.) Unless I'm not understanding the architecture, the project would have escaped your ability to control it.