You are viewing a single comment's thread from:
RE: What Would "Controlling Your Own Data" Actually Look Like on Steem?
Will watch it tonight. Thanks.
I would love this to happen but with three additional features (on is quite hard to come up without centralizing stuff)...
- In addition to encryption, have something like "time I want this to be encrypted". And then after the time expires, the data would be seen as not encrypted forever.
- Partial encryption within unencrypted text. When we want to target great audiences but restrict some comments to only a few people.
- Sourced Expiring Encryption: What you share is an encrypted location of the source of something else that is per-si encrypted too (like a picture). Only the person with the password of the encrypted source location is able to decrypt the source too, but only during a certain time. Afterwards, the source content is either deleted (for sources where that is possible to guarantee, therefore not within the blockchain) or re-encrypted with a random password (and follows that pattern forever) - this last one works with blockchain "contracts".
Yeah, that would be interesting. Maybe each post could simply be modified to include a decryption key and, if that is set, decrypt the post before displaying it. That wouldn't be automatic, but you could at least, at a later date, modify a post to include the decryption key.
Yeah, that would be easy enough just to decide, in the editor maybe, what you'd like to encrypt. You could then select the text, right, click and select "encrypt" maybe with some options for who sees it (followers only, a selected list of followers, etc).
This one has me confused. Nothing can be deleted on a blockchain, as you said, so I'm not quite sure how that applies here.
For No 3, if it cannot be deleted, then at least be edited to blank ??
#3 uses a third location... the blockchain metadata will be there still (and unchanged) but pointing to nothing after the third location is "forfeited"...
Basically after the timeout, you should not "believe in the destination". Kind of like pointing to an IPFS location that has encoded data pointing you somewhere with a dependency on time. After that "particular" time, the decoder will show you nothing... or something not useful.
Assuming you know the password, you can reverse clock back and if the source is still available, see the data, but if you don't know the password... it is useless...
I know it's not perfect... and I am still thinking about how to make it bullet proof... but so far, I like the idea.
Interesting. So something like snapchat where the content only lives for a short period of time. It seems somewhat centralized to me.
It is, that was the part I was trying to say that is hard to decentralize (at least to my knowledge).