create account

RE: What Would "Controlling Your Own Data" Actually Look Like on Steem? by lukestokes

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @forykw/re-lukestokes-2019726t175624422z

· @lukestokes ·
1. 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.

1. 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).

1. 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.
properties (22)
authorlukestokes
permlinkpv95p8
categoryprivacy
json_metadata{"tags":["privacy"],"app":"steemit/0.1"}
created2019-07-26 14:03:09
last_update2019-07-26 14:03:09
depth2
children4
last_payout2019-08-02 14:03:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length666
author_reputation556,640,380,599,219
root_title"What Would "Controlling Your Own Data" Actually Look Like on Steem?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,770,408
net_rshares0
@forykw · (edited)
#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.
properties (22)
authorforykw
permlinkre-lukestokes-2019727t2228898z
categoryprivacy
json_metadata{"tags":["privacy"],"app":"esteem/2.1.0-surfer","format":"markdown+html","community":"esteem.app"}
created2019-07-26 14:22:09
last_update2019-07-26 14:23:30
depth3
children2
last_payout2019-08-02 14:22:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length722
author_reputation94,636,186,753,302
root_title"What Would "Controlling Your Own Data" Actually Look Like on Steem?"
beneficiaries
0.
accountesteemapp
weight1,000
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,771,111
net_rshares0
@lukestokes ·
Interesting. So something like snapchat where the content only lives for a short period of time. It seems somewhat centralized to me.
properties (22)
authorlukestokes
permlinkpv978q
categoryprivacy
json_metadata{"tags":["privacy"],"app":"steemit/0.1"}
created2019-07-26 14:36:27
last_update2019-07-26 14:36:27
depth4
children1
last_payout2019-08-02 14:36:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length133
author_reputation556,640,380,599,219
root_title"What Would "Controlling Your Own Data" Actually Look Like on Steem?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,771,509
net_rshares0
@forykw ·
It is, that was the part I was trying to say that is hard to decentralize (at least to my knowledge).
properties (22)
authorforykw
permlinkre-lukestokes-2019727t115943216z
categoryprivacy
json_metadata{"tags":["privacy"],"app":"esteem/2.1.0-surfer","format":"markdown+html","community":"esteem.app"}
created2019-07-26 23:59:45
last_update2019-07-26 23:59:45
depth5
children0
last_payout2019-08-02 23:59:45
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length101
author_reputation94,636,186,753,302
root_title"What Would "Controlling Your Own Data" Actually Look Like on Steem?"
beneficiaries
0.
accountesteemapp
weight1,000
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,787,982
net_rshares0
@sanjeevm ·
$0.14
For No 3, if it cannot be deleted, then at least be edited to blank ??
👍  , , , , ,
properties (23)
authorsanjeevm
permlinkpvafgx
categoryprivacy
json_metadata{"tags":["privacy"],"app":"steemit/0.1"}
created2019-07-27 06:31:42
last_update2019-07-27 06:31:42
depth3
children0
last_payout2019-08-03 06:31:42
cashout_time1969-12-31 23:59:59
total_payout_value0.102 HBD
curator_payout_value0.033 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length70
author_reputation746,804,177,890,005
root_title"What Would "Controlling Your Own Data" Actually Look Like on Steem?"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id88,797,161
net_rshares387,388,687,558
author_curate_reward""
vote details (6)