[shazow]

Right, we were worried about this also. The best solution we could think of is include an NSFW flag on ads that an admin (myself and Max) can force, which prevents the ad from being rendered by default.

The "bad bytes" are still out there, but at least we don't have to subject the consumers of our frontend to it unless they opt in.

[jasode]

>, 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.

[shazow]

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.

[thisisit]

I am wondering what capabilities do you guys have as admins other than the NSFW flag? And how does the NSFW flag affect the rendering when using Mist or Parity?

[shazow]

We control the presentation layer (the domain, the VueJS app). If you're using our presentation layer, then you're essentially rendering what we programmed to be rendered. In this case, NSFW is default not rendered but you can toggle it in the footer.

If someone forks our presentation layer, they can launch it on another domain to do whatever they want.

[thisisit]

But...if some ad buyer doesn't set the NSFW flag then how do you control the presentation layer? Can you guys actually set the flag later then?