Viewing a response to: @watervapor/re-dantheman-steem-and-bitshares-cryptographic-security-update-20170224t211227734z
We have many JS libraries that could be used off the shelf that already implement proper canonical signature signing.
| post_id | 2,037,021 |
|---|---|
| author | dantheman |
| permlink | re-watervapor-re-dantheman-steem-and-bitshares-cryptographic-security-update-20170224t221437083z |
| category | steem |
| json_metadata | "{"app": "steemit/0.1", "tags": ["steem"]}" |
| created | 2017-02-24 22:14:36 |
| last_update | 2017-02-24 22:14:36 |
| depth | 2 |
| children | 7 |
| net_rshares | 1,431,321,544,354 |
| last_payout | 2017-03-28 00:32:33 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.134 SBD |
| curator_payout_value | 0.011 SBD |
| pending_payout_value | 0.000 SBD |
| promoted | 0.000 SBD |
| body_length | 117 |
| author_reputation | 240,497,801,758,545 |
| root_title | "Steem & BitShares Cryptographic Security Update" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 SBD |
| percent_steem_dollars | 10,000 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| sandwich | 0 | 11,399,987,098 | 100% | ||
| christoph3 | 0 | 7,760,643,870 | 100% | ||
| ausbitbank | 0 | 127,120,700,282 | 100% | ||
| krystle | 0 | 36,878,599,826 | 100% | ||
| bitcoiner | 0 | 45,159,400,420 | 100% | ||
| dirty.hera | 0 | 190,784,672 | 100% | ||
| steemleak | 0 | 5,025,000,726 | 100% | ||
| ekitcho | 0 | 735,879,928,802 | 100% | ||
| l0k1 | 0 | 207,492,430,645 | 100% | ||
| anagamidev | 0 | 253,880,503,680 | 100% | ||
| johnathanhenry | 0 | 75,219,266 | 76% | ||
| johnthehoan | 0 | 291,175,156 | 100% | ||
| mestyz | 0 | 116,144,418 | 100% | ||
| kamidela | 0 | 51,025,493 | 100% |
You are no doubt right. My intention with this post was instead to the address the lack of trust between the two projects (and indeed, in the broader crypto community). I think we can do better than we're doing.
| post_id | 2,038,959 |
|---|---|
| author | watervapor |
| permlink | re-dantheman-re-watervapor-re-dantheman-steem-and-bitshares-cryptographic-security-update-20170225t071502092z |
| category | steem |
| json_metadata | "{"app": "steemit/0.1", "tags": ["steem"]}" |
| created | 2017-02-25 07:15:12 |
| last_update | 2017-02-25 07:15:12 |
| depth | 3 |
| children | 5 |
| net_rshares | 402,947,892,289 |
| last_payout | 2017-03-28 00:32:33 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 SBD |
| curator_payout_value | 0.000 SBD |
| pending_payout_value | 0.000 SBD |
| promoted | 0.000 SBD |
| body_length | 211 |
| author_reputation | 37,631,848,837 |
| root_title | "Steem & BitShares Cryptographic Security Update" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 SBD |
| percent_steem_dollars | 10,000 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| tuck-fheman | 0 | 402,947,892,289 | 100% |
I think the way in which we could do better is to all stop making excuses for @faddat's unwarranted tantrums and mudslinging. The code is there for him to review, and all the demands he was making could have been resolved by him taking 5 minutes to read it. (He even had three experienced devs helping him in the comments in the linked thread.) Instead, he chose to (in order): assign blame, be passive aggressive, play the victim, and then speculate about malice—without basis. We are all now aware of how productive these behaviors turned out to be. He shouldn't have to speculate very much more to figure out why he is unwelcome in our Slack. We welcome constructive feedback, positive *and* negative. This wasn't that. We are a very small team and reading and responding to this sort of toxic behavior has tangible effects on our productivity.
| post_id | 2,039,166 |
|---|---|
| author | sneak |
| permlink | re-watervapor-re-dantheman-re-watervapor-re-dantheman-steem-and-bitshares-cryptographic-security-update-20170225t083714770z |
| category | steem |
| json_metadata | "{"app": "steemit/0.1", "users": ["faddat"], "tags": ["steem"]}" |
| created | 2017-02-25 08:37:15 |
| last_update | 2017-02-25 09:12:48 |
| depth | 4 |
| children | 4 |
| net_rshares | 1,067,364,257,321 |
| last_payout | 2017-03-28 00:32:33 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.077 SBD |
| curator_payout_value | 0.008 SBD |
| pending_payout_value | 0.000 SBD |
| promoted | 0.000 SBD |
| body_length | 852 |
| author_reputation | 27,542,287,033,381 |
| root_title | "Steem & BitShares Cryptographic Security Update" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 SBD |
| percent_steem_dollars | 10,000 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| roelandp | 0 | 947,934,324,383 | 100% | ||
| ausbitbank | 0 | 119,429,932,938 | 100% |
>he chose to (in order): assign blame, be passive aggressive, play the victim, and then speculate about malice—without basis. Not to mention the DAWN project which I believe he is involved in and their recent cointelegraph article, with the timing in mind you could very well class this as pure FUD.
| post_id | 2,047,884 |
|---|---|
| author | acidyo |
| permlink | re-sneak-re-watervapor-re-dantheman-re-watervapor-re-dantheman-steem-and-bitshares-cryptographic-security-update-20170226t201345718z |
| category | steem |
| json_metadata | "{"app": "steemit/0.1", "tags": ["steem"]}" |
| created | 2017-02-26 20:13:45 |
| last_update | 2017-02-26 20:13:45 |
| depth | 5 |
| children | 3 |
| net_rshares | 207,795,813,093 |
| last_payout | 2017-03-28 00:32:33 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.070 SBD |
| curator_payout_value | 0.023 SBD |
| pending_payout_value | 0.000 SBD |
| promoted | 0.000 SBD |
| body_length | 300 |
| author_reputation | 1,572,775,251,470,663 |
| root_title | "Steem & BitShares Cryptographic Security Update" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 SBD |
| percent_steem_dollars | 10,000 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| l0k1 | 0 | 207,492,430,645 | 100% | ||
| johnthehoan | 0 | 303,382,448 | 100% |
We didn't want to use javascript, @dantheman. We wanted to use go so we could integrate it on the back end and achieve more than a superficial integration. Since you wrote graphene in C++ I'm sure you know what I'm talking about regarding javascript vs actual systems programming languages like C, C++, java, go, or rust. Ain't no beef in the land of javascript by comparison. If you want beef, you've got to go lower level, and we wanted to build beefy steem integrations. Please, don't tell me you think your js libs make it all okay, because I know that you know they don't. Now that @baabeetaa has the answers he needed, we will be integrating on the back end, because @baabeetaa is a badass.
| post_id | 2,081,108 |
|---|---|
| author | faddat |
| permlink | re-dantheman-re-watervapor-re-dantheman-steem-and-bitshares-cryptographic-security-update-20170304t004011951z |
| category | steem |
| json_metadata | "{"app": "steemit/0.1", "users": ["dantheman", "baabeetaa"], "tags": ["steem"]}" |
| created | 2017-03-04 00:40:12 |
| last_update | 2017-03-04 01:27:27 |
| depth | 3 |
| children | 0 |
| net_rshares | 0 |
| last_payout | 2017-03-28 00:32:33 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 SBD |
| curator_payout_value | 0.000 SBD |
| pending_payout_value | 0.000 SBD |
| promoted | 0.000 SBD |
| body_length | 703 |
| author_reputation | 36,587,550,369,900 |
| root_title | "Steem & BitShares Cryptographic Security Update" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 SBD |
| percent_steem_dollars | 10,000 |