I already have a pretty hard time with SEO spammers rephrasing the content I live from and passing it as their own. I can't imagine people lifting the entire website and making a permanent copy of it, profiting from 4 years of my work.
That's for a 100% free website with no "secret sauce" besides hard work. I can imagine any other website might want to hold their cards even closer.
Then there's also the site owners being held responsible for hosting illegal content, and being powerless to delete it.
There's no way I'd want to create something that is similar to what you're thinking, because it's pointless as you are thinking. Nobody would pay for this. Also messages such as these have no reason to be on an immutable blockchain. But you can certainly create specialized services for people that support your projects using ideas like this quite seemlessly.
And the fee thing is why none of this will work in practice so it’s a really big negative. Who on Earth wants to be nickel and dimed across the Internet for really over expensive compute and storage?
But:
* The fact that the moderators have access to these mechanisms would be known by all users
* The use of these mechanisms by moderators would be public. If a topic is upped by a moderator, it would be logged in the blockchain. No moderator would be able to do it secretly.
Regarding the fee, it's true that it's a big downside. To get a feasible use case, the devs would need to find a blockchain that reduces them.You're providing a solution that doesn't fit the initial requirement of a system being trust-less. So, indeed, your solution works, but as you described, it requires trust in the administrators of the website. The idea of web3 is that you wouldn't. "Trust but verify", if you want.
This could be used for Facebook or Reddit (given that they solve or attenuate the issue of fees), where people might have less trust in the administrators.
For stuff at the scale of Facebook and Reddit you'd also probably end up needing caching as the chains would be too slow so you end up needing a layer of trust anyway.
I’d also add keeping an eternal, permanent, public record of everything as a big downside.
What about the right to be forgotten and GDPR laws?
A blockchain is essentially an Event Sourced system. And Right To Be Forgotton is a common issue in all event sourced systems.
Several technical and one non technical solution are common:
Encrypt events with per actor keys. Delete the key when user wants to be forgotton. Or encrypt just certain attributes in the same way.
Keep actual data outside of events but only include a link to the data and checksum of the data.
Avoid storing PII in the first place. Does your domain model really require an IPaddress or First Name?
All have tradeoffs, none are silver bullets. But it is a solved problem in Event Sourcing, so it is a solved problem with blockchains (if only new programmers new this and reused patters instead of continually reinventing them)
You're saying this:
> Encrypt events with per actor keys. Delete the key when user wants to be forgotton.
Blockchain is immutable. Which key are you going to delete? Or, wait, you're going to centrally store these keys?
No necessarily. Three alternatives are common:
Data is encrypted with a key only the actor owns. Works for cases where that actor is the only one who should access it (I Reveal My Attributes type of schemes)
Data is encrypted with a sum (combination) of the key from an actor plus some other actors have: only you and the recipient can decrypt. Works for cases like messaging or p2p data exchange.
Data is encrypted with a OR of the key from an actor plus one by a trusted proxy: proxy and actor have ability to decrypt. This is closest the "centrally" storing. With the difference that "proxy" allows for a little more flexibity -in theory-.
Similarly storing all the data off the blockchain just means you didn’t need a blockchain.