create account

RE: Let Zappl Clerify some things. FUD Correction by zappl

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

Viewing a response to: @reggaemuffin/re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180212t170047958z

· @zappl · (edited)
$1.49
Please read to the bottom of me and inertia conversation. We don't save keys.
👍  ,
properties (23)
authorzappl
permlinkre-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t020456698z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1"}
created2018-02-13 02:04:57
last_update2018-02-13 02:05:18
depth3
children9
last_payout2018-02-20 02:04:57
cashout_time1969-12-31 23:59:59
total_payout_value1.487 HBD
curator_payout_value0.004 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length77
author_reputation41,244,449,218,741
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,081,279
net_rshares205,693,999,256
author_curate_reward""
vote details (2)
@elmubareki ·
$0.02
They do not believe it yet. And With time, they will believe.

## Zappl just has to keep giving trust to users, that's all. And Never make mistakes.
👍  
properties (23)
authorelmubareki
permlinkre-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t021239158z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1"}
created2018-02-13 02:13:15
last_update2018-02-13 02:13:15
depth4
children4
last_payout2018-02-20 02:13:15
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length148
author_reputation22,740,889,959,243
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,082,892
net_rshares3,012,644,096
author_curate_reward""
vote details (1)
@reggaemuffin ·
$0.11
They already did make mistakes, and since it is open source, their mistakes are public record.

If they still say that keys are safe they either have no clue at all or made a big mistake they try to talk down instead of fixing.
👍  , , , ,
properties (23)
authorreggaemuffin
permlinkre-elmubareki-re-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t061426985z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1"}
created2018-02-13 06:14:27
last_update2018-02-13 06:14:27
depth5
children3
last_payout2018-02-20 06:14:27
cashout_time1969-12-31 23:59:59
total_payout_value0.114 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length227
author_reputation37,964,839,695,531
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,131,994
net_rshares16,074,772,705
author_curate_reward""
vote details (5)
@zappl · (edited)
Well one there was no active keys being saved so even if it was closed the issue wasn't keys being saved. It was in the possibility of them being saved in an error for the transaction if said node was down. 

Which wasn't discovered until today, this was not even listed in the ticket. There was no intentional attempt to lie.

Yes we should have replied saying no we don't save keys but me an inertia had these talks before. Its not till recently that we found they could be saved by mistake in log files. 

There was no keys in the logged file because the error would be in certain circumstances that were even less likely with us load balancing.

Find out more here:
https://github.com/Zappl/Zappl/issues/5#issuecomment-365120779 And please feel free to go through me an inertia back and forth which is very public.
👍  , ,
properties (23)
authorzappl
permlinkre-reggaemuffin-re-elmubareki-re-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t064217555z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1","links":["https://github.com/Zappl/Zappl/issues/5#issuecomment-365120779"]}
created2018-02-13 06:42:18
last_update2018-02-13 06:45:24
depth6
children2
last_payout2018-02-20 06:42:18
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_length818
author_reputation41,244,449,218,741
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,137,010
net_rshares1,454,527,503
author_curate_reward""
vote details (3)
@reggaemuffin ·
Seems you don't save keys, but if they so happen to be leaked in logs, the fix for that will take weeks?

I am not impressed by how you handled this and will advise everyone to change their keys if they used zappl. 

Should you have the fix live at some point, please comment on the github issue.
👍  
properties (23)
authorreggaemuffin
permlinkre-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t061003059z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1"}
created2018-02-13 06:10:03
last_update2018-02-13 06:10:03
depth4
children2
last_payout2018-02-20 06:10:03
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_length296
author_reputation37,964,839,695,531
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,131,174
net_rshares2,783,737,854
author_curate_reward""
vote details (1)
@zappl · (edited)
$0.37
No this fix shouldn't take weeks. Also the issues is the node crashes well we load balance so the chances are low. But just in case we will be adjusting what is logged in the failure of said transaction.

Zappl didn't try to hide anything, just not used to having to comment on bug reports. This is our first Open source project so we wasn't used to always given feed back. But as you stated it was unprofessional of us to just look over problem. 

@thedegensloth and @inertia have talk about this issue before privately before. But till today it didn't reach the point of were we found the bug report saving issue which has never occurred.  

We were being truthful when we said we didn't store keys, but there was a issue we didn't think about. Which is why zappl is open source. So we've been working on browserify methods which will be coming. 

But the temp method will be modifying what shows up in the logs. We thank you for your concern and realize our fault and hope we can continue to earn everyone trust.
👍  , ,
properties (23)
authorzappl
permlinkre-reggaemuffin-re-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t061620909z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1","users":["thedegensloth","inertia"]}
created2018-02-13 06:16:21
last_update2018-02-13 06:30:36
depth5
children1
last_payout2018-02-20 06:16:21
cashout_time1969-12-31 23:59:59
total_payout_value0.280 HBD
curator_payout_value0.085 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,015
author_reputation41,244,449,218,741
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,132,344
net_rshares50,709,751,397
author_curate_reward""
vote details (3)
@reggaemuffin ·
$0.11
Thank you for this! Being open source means accepting that there will be bugs and reacting to them publicly. And I am glad that you are open about this issue.
👍  , , , ,
properties (23)
authorreggaemuffin
permlinkre-zappl-re-reggaemuffin-re-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t075525660z
categoryzappl
json_metadata{"tags":["zappl"],"app":"steemit/0.1"}
created2018-02-13 07:55:24
last_update2018-02-13 07:55:24
depth6
children0
last_payout2018-02-20 07:55:24
cashout_time1969-12-31 23:59:59
total_payout_value0.110 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length158
author_reputation37,964,839,695,531
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,150,801
net_rshares15,590,468,154
author_curate_reward""
vote details (5)
@richalyandesty ·
Oke sir zappl thank you
properties (22)
authorrichalyandesty
permlinkre-zappl-re-reggaemuffin-re-inertia-re-zappl-let-zappl-clerify-some-things-fud-correction-20180213t033903577z
categoryzappl
json_metadata{"tags":["zappl"],"community":"busy","app":"busy/2.3.0"}
created2018-02-13 03:39:09
last_update2018-02-13 03:39:09
depth4
children0
last_payout2018-02-20 03:39: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_length23
author_reputation772,042,122,996
root_title"Let Zappl Clerify some things. FUD Correction"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id37,100,224
net_rshares0