Viewing a response to: @beanz/re-inertia-re-beanz-de-centralised-captcha-system-20170109t170531731z
The interesting thing about making it optional for each post is that certain content becomes a needle-in-the-haystack. That way, bots aren't instantly useless once CAPTCHAs become a thing. As for creating an incentive, maybe a drastic solution is that CAPTCHA-enabled posts get their own dedicated reward pool. Maybe there's a less drastic way to go about it like a witness-defined reward multiplier parameter.
| author | inertia |
|---|---|
| permlink | re-beanz-re-inertia-re-beanz-de-centralised-captcha-system-20170109t171447383z |
| category | curation |
| json_metadata | {"tags":["curation"]} |
| created | 2017-01-09 17:14:45 |
| last_update | 2017-01-09 17:14:57 |
| depth | 3 |
| children | 3 |
| last_payout | 2017-02-09 17:28:39 |
| 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 | 413 |
| author_reputation | 346,568,901,399,561 |
| root_title | "De-centralised CAPTCHA system (Part 2 of 3)" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 2,204,306 |
| net_rshares | 56,947,233,018 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| beanz | 0 | 56,947,233,018 | 100% |
That's an interesting idea and would be a nice way to ease everybody into it. I still don't think they should appear for every vote, but more on that in the next post. :)
| author | beanz |
|---|---|
| permlink | re-inertia-re-beanz-re-inertia-re-beanz-de-centralised-captcha-system-20170109t194141968z |
| category | curation |
| json_metadata | {"tags":["curation"]} |
| created | 2017-01-09 19:41:45 |
| last_update | 2017-01-09 19:41:45 |
| depth | 4 |
| children | 0 |
| last_payout | 2017-02-09 17:28:39 |
| 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 | 172 |
| author_reputation | 77,215,574,122,930 |
| root_title | "De-centralised CAPTCHA system (Part 2 of 3)" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 2,205,525 |
| net_rshares | 0 |
If they were to create their own dedicated pool, where would the steem for the rewards come from? I think having the choice to enable this is a good idea, that way those who like bots can continue to have them upvote their posts, and those who don't can exclude them (Even though it is certainly possible to program a bot that gets through CAPTCHA). I don't see why a separate rewards pool is necessary (I don't think it is possible to make another rewards pool Steem can't just appear out of nowhere), maybe a separate category like the promote category. Anyway, I think having it so it can be turned on or off varying on the author is a good idea, so thanks for sharing that idea!
| author | cmp2020 |
|---|---|
| permlink | re-inertia-re-beanz-re-inertia-re-beanz-de-centralised-captcha-system-20170110t050034220z |
| category | curation |
| json_metadata | {"tags":["curation"]} |
| created | 2017-01-10 05:00:42 |
| last_update | 2017-01-10 05:00:42 |
| depth | 4 |
| children | 1 |
| last_payout | 2017-02-09 17:28:39 |
| 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 | 682 |
| author_reputation | 65,599,003,109,574 |
| root_title | "De-centralised CAPTCHA system (Part 2 of 3)" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 2,209,324 |
| net_rshares | 0 |
There have been suggestions in the past about having different pools. It's called segregated reward pools. Technically, it's all coming from the same pool, but they're segmented and dedicated to different goals. I think the real solution is to have completely separate areas like "substeems" with their own reward pools and smart contracts. Smart contracts would allow different rules for each substeem, like how CAPTCHAs are implemented. I go over the full idea here: https://steemit.com/steemit/@inertia/substeem
| author | inertia |
|---|---|
| permlink | re-cmp2020-re-inertia-re-beanz-re-inertia-re-beanz-de-centralised-captcha-system-20170110t050924216z |
| category | curation |
| json_metadata | {"tags":["curation"],"links":["https://steemit.com/steemit/@inertia/substeem"]} |
| created | 2017-01-10 05:09:24 |
| last_update | 2017-01-10 05:09:24 |
| depth | 5 |
| children | 0 |
| last_payout | 2017-02-09 17:28:39 |
| 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 | 521 |
| author_reputation | 346,568,901,399,561 |
| root_title | "De-centralised CAPTCHA system (Part 2 of 3)" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 2,209,364 |
| net_rshares | 18,885,912,219 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| mughat | 0 | 18,885,912,219 | 100% |
hiveblocks