Viewing a response to: @reazuliqbal/q4icoi
I ended up going different way. Server encode a token/secret using user's public key. Then user decode it using `steem_keychain.requestVerifyKey`. If successful then we got a handshake for the future.
author | mys |
---|---|
permlink | re-reazuliqbal-q4jzmm |
category | steemdev |
json_metadata | {"tags":["steemdev"],"app":"steempeak/2.2.8"} |
created | 2020-01-23 09:28:00 |
last_update | 2020-01-23 09:28:00 |
depth | 3 |
children | 1 |
last_payout | 2020-01-30 09:28:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.016 HBD |
curator_payout_value | 0.015 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 200 |
author_reputation | 14,948,575,541,320 |
root_title | "How to Use Steem Keychain Login in Your Node JS Website/API" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 94,678,463 |
net_rshares | 204,684,225,940 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
steemtaker | 0 | 41,276,494,097 | 30% | ||
reazuliqbal | 0 | 88,201,865,351 | 30% | ||
socialbot | 0 | 75,205,866,492 | 15% |
It could be better in some cases than the way I wrote about. I am guessing we need to send 2 requests, one for fetching encoded message, another letting server know use successfully decoded the message. But I think its more secured in some use cases. Thanks for sharing the idea.
author | reazuliqbal |
---|---|
permlink | q4jzz8 |
category | steemdev |
json_metadata | {"app":"steemit/0.1"} |
created | 2020-01-23 09:35:33 |
last_update | 2020-01-23 09:35:33 |
depth | 4 |
children | 0 |
last_payout | 2020-01-30 09:35:33 |
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 | 280 |
author_reputation | 61,984,354,446,410 |
root_title | "How to Use Steem Keychain Login in Your Node JS Website/API" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 94,678,739 |
net_rshares | 54,923,013,175 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
noblebot | 0 | 39,350,502,714 | 100% | ||
rabbitbot | 0 | 15,572,510,461 | 100% |