Viewing a response to: @steemitblog/engineering-update-mira-testing-in-production
Thatโs freakinโ awesome! Canโt wait for SMT to come out in the near future! ๐ช๐ผ๐๐ผ๐ฏ
author | stackin |
---|---|
permlink | stackin-re-steemitblog-engineering-update-mira-testing-in-production-20190328t200651561z |
category | steem |
json_metadata | {"app":"partiko","client":"ios"} |
created | 2019-03-28 20:06:51 |
last_update | 2019-03-28 20:09:51 |
depth | 1 |
children | 5 |
last_payout | 2019-04-04 20:06:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.028 HBD |
curator_payout_value | 0.002 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 81 |
author_reputation | 833,057,026,588,099 |
root_title | "Engineering Update: MIRA Testing in Production!" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 82,115,485 |
net_rshares | 55,153,274,970 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
theb0red1 | 0 | 3,192,350,182 | 10% | ||
tarazkp | 0 | 51,899,743,693 | 11% | ||
ackza | 0 | 61,181,095 | 1% |
WOAH wait did you read them say they have a Private Key PDF backup system? I hope that they arent just having users download a PDF with a private key to their desktop environment? I have an old Github post answered by @smittyvb where I ask about backing up of owner keys and he explains how to remedy this situation with clever thinking: > this situation could also be helped by having @steemit store account keys for a few days after creation. Advanced users would be able to change their password to revoke Steemitโs access, but normal users would have a password reset functionality. This could also be implemented as giving the Steemit account owner authority, then have Steemit revoke itself. https://github.com/steemit/condenser/issues/2921 Also >During this process we are continuing to test and improve the Social Condenser application we have running in our development environment. @steemitblog can we PLEASE see a low res blurry screenshot of the new condenser social app? Please tell me you have updated the GUI like golos.io did at least? And also when will we get to skin the front end the way we want like winamp skins?
author | ackza |
---|---|
permlink | re-stackin-stackin-re-steemitblog-engineering-update-mira-testing-in-production-20190328t222059285z |
category | steem |
json_metadata | {"tags":["steem"],"users":["smittyvb","steemit","steemitblog"],"app":"steemit/0.1","links":["https://github.com/steemit/condenser/issues/2921"]} |
created | 2019-03-28 22:21:00 |
last_update | 2019-03-28 22:25:06 |
depth | 2 |
children | 4 |
last_payout | 2019-04-04 22:21:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,140 |
author_reputation | 288,240,462,642,811 |
root_title | "Engineering Update: MIRA Testing in Production!" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 82,122,618 |
net_rshares | 0 |
We do not, never have, and never will store user's private keys for any period of time. There are some other interesting ideas that could be discussed to help prevent lost keys, but storing keys for any period of time is not one of them ๐๐๐๐๐
author | justinw |
---|---|
permlink | re-ackza-re-stackin-stackin-re-steemitblog-engineering-update-mira-testing-in-production-20190329t024201588z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2019-03-29 02:42:00 |
last_update | 2019-03-29 02:45:45 |
depth | 3 |
children | 3 |
last_payout | 2019-04-05 02:42:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.552 HBD |
curator_payout_value | 0.169 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 244 |
author_reputation | 15,502,058,309,908 |
root_title | "Engineering Update: MIRA Testing in Production!" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 82,130,187 |
net_rshares | 1,073,689,450,314 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
ackza | 0 | 8,572,276,668 | 85% | ||
destinysaid | 0 | 396,142,010,314 | 77% | ||
surfyogi | 0 | 587,726,495,708 | 50% | ||
tytran | 0 | 58,199,562,608 | 36% | ||
eastmael | 0 | 23,049,105,016 | 100% |
Yeah but allowing users to unsafely download their own private key as a PDF, which many will forget about, its irresponsible, and i never said anything about storing the users keys, i dunno where you got that, its like you didnt even read what i wrote at all, I am talking about giving @steemit permission for a 30 day period over new accounts, incase they loose the keys, and giving users ability to opt out of this 30 day period, from the beginning, but its really important for all the people who loose their key I read recently something about this and it is so vague and sounds dangerous >To help mitigate these issues in the short term, we have been working on a solution that renders a PDF containing all of a userโs Keys and their Master Password upon request, and strongly suggests that they print it out as a backup. https://steemit.com/steemit/@steemitblog/engineering-update-condenser-split-key-backup-mira I never said steenmit should save the key but you can still give @steemit owner permissions as discussed in the github page on condenser, im talking about a hypothetical future feature i dont think giving people a PDF document is a very good idea, thats just going to be saved on the persons desktop or smartphone?
author | ackza |
---|---|
permlink | re-justinw-re-ackza-re-stackin-stackin-re-steemitblog-engineering-update-mira-testing-in-production-20190329t025058824z |
category | steem |
json_metadata | {"tags":["steem"],"users":["steemit"],"links":["https://steemit.com/steemit/@steemitblog/engineering-update-condenser-split-key-backup-mira"],"app":"steemit/0.1"} |
created | 2019-03-29 02:51:00 |
last_update | 2019-03-29 02:51:00 |
depth | 4 |
children | 0 |
last_payout | 2019-04-05 02:51:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,240 |
author_reputation | 288,240,462,642,811 |
root_title | "Engineering Update: MIRA Testing in Production!" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 82,130,582 |
net_rshares | 0 |
Yeah, I get you Justin. That's cool. @ackza, it would take a DB at steemit.com to do what you propose, definately not cool.. Meanwhile, this is a difficult problem and writing a file to the user's disk, is not cool either. I propose (for lack of better idea?): 1) tel user to get 2 flash drives. 2) copy and paste directly to the flash drive, a new text file. 3) copy and paste the pass info to a new text file on a flash drive. 4) Copy the data from one flash drive, to the second flash drive. 5) Lock each flash drive into a safe in separate buildings.
author | surfyogi |
---|---|
permlink | re-justinw-re-ackza-re-stackin-stackin-re-steemitblog-engineering-update-mira-testing-in-production-20190329t050250463z |
category | steem |
json_metadata | {"tags":["steem"],"users":["ackza"],"app":"steemit/0.1"} |
created | 2019-03-29 05:02:51 |
last_update | 2019-03-29 05:07:15 |
depth | 4 |
children | 1 |
last_payout | 2019-04-05 05:02:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.044 HBD |
curator_payout_value | 0.014 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 554 |
author_reputation | 31,155,045,810,316 |
root_title | "Engineering Update: MIRA Testing in Production!" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 82,135,102 |
net_rshares | 86,828,608,433 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
justinw | 0 | 86,828,608,433 | 20% |