This is why most blogs would opt to use a trusted provider like steemit.com and use an iframe to host comments.
It should be easy enough to have a "key per provider" so that you know which provider was hacked.
You are viewing a single comment's thread from:
Revocable delegate keys would enable this, it also helps with curation guilds, per app passwords like Google has. And you could add later secret share keys that enable an x of y override key for such as death, coma and other forms of becoming legally incompetent (Facebook has something like this since so many users had died...).
It may be worth considering updates to the private keys to allow users to place additional restrictions on what individual posting keys are allowed to do. For example restricting the domain that they can interact in. If there was also a way to force the external sites to use a separate key, that would probably be good too. This would greatly reduce the risk of malicious third party sites taking advantage of users private keys.
Exactly!
But I would be against of forcing a user to dealing with all those keys, because for average users those things are already really complicated and new. What do you think about concept of slaves accounts: https://steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives#@noisy/re-timcliff-re-noisy-re-steemitblog-proposed-upgrade-for-blockchain-incentives-20161119t122443054z