Viewing a response to: @steemitblog/hf20-update-operations-stable
The RC system still needs a little bit of work. Post and comments need to be separated out, and separate from each other. they are two different aspects of steemit. Once the separation is complete then constraints need to be put in place. The vast majority of spam comes in the form of comments. As I suggested in a comment to @paulag there needs to be a timer put on them: > Example second post in less than 2 hours cost twice as much RC to post, third one in less than two hours after the second one then four times the cost of the second. That would take care of some of the rapid fire posting. Two hour time frame is a reasonable time frame, this will I understand hurt things like the pull into steem apps stream2steem or whatever they are called. So not rapid fire twitter recast or steepshot recast or things of that nature. The app designers will just have to look at the time frames. >To really do away with the comment spam, second comment in less than 3 sec's ten times the cost, 3 in less than 6 sec's from the first 100 times the cost. end of bot spam. This would of course seriously curtail the ability of any vote bots to have their advertisement show on the post that paid for their use but, such is life, the bot's would still be able to vote, and that is one thing that should not have a time limit because of curation trails and bot votes. This will no likely cause a lot more kick back than the posting issues, but the vote bots can adjust their commands to comment only once every 2 or three minutes. Just a couple of thoughts.
author | bashadow |
---|---|
permlink | re-steemitblog-hf20-update-operations-stable-20181001t214034029z |
category | steem |
json_metadata | {"tags":["steem"],"users":["paulag"],"app":"steemit/0.1"} |
created | 2018-10-01 21:40:33 |
last_update | 2018-10-01 21:40:33 |
depth | 1 |
children | 10 |
last_payout | 2018-10-08 21:40: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 | 1,553 |
author_reputation | 100,388,692,638,882 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,439,214 |
net_rshares | 0 |
what if someone creates a twitter clone where people would like to share stuff every minute? The blockchain steem was made for all kind of dapps, not only steemit.com.
author | geronimo |
---|---|
permlink | re-bashadow-re-steemitblog-hf20-update-operations-stable-20181001t214921423z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 21:49:21 |
last_update | 2018-10-01 21:49:48 |
depth | 2 |
children | 6 |
last_payout | 2018-10-08 21:49:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.115 HBD |
curator_payout_value | 0.037 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 167 |
author_reputation | 2,923,721,121,912 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,439,565 |
net_rshares | 79,558,642,240 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
stimialiti | 0 | -3,684,741,480 | -100% | ||
kabir88 | 0 | 83,243,383,720 | 100% |
Steemit does not control the blockchain, RC's are for steemit. It is my understanding that Dapps will have to pay their own way on the chain. So if a dapp wants to create a twitter resteamer, then the dapp and dapp user are going to have to pay the RC cost of the posting. They have not been silenced it just that it cost them more to post. "I had eggs for breakfast. What did you have" with a picture of their breakfast.
author | bashadow |
---|---|
permlink | re-geronimo-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181001t215527690z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 21:55:27 |
last_update | 2018-10-01 21:55:27 |
depth | 3 |
children | 5 |
last_payout | 2018-10-08 21:55:27 |
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 | 421 |
author_reputation | 100,388,692,638,882 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,439,803 |
net_rshares | 0 |
No, RCs are for all Steem DApps. Nothing is specific to steemit.com. A transaction on steemit.com will cost just as much in RCs as the same transaction on another Steem DApp like a twitter clone.
author | andrarchy |
---|---|
permlink | re-bashadow-re-geronimo-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181001t220037781z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 22:00:39 |
last_update | 2018-10-01 22:00:39 |
depth | 4 |
children | 1 |
last_payout | 2018-10-08 22:00: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 | 195 |
author_reputation | 230,168,201,522,782 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 0.000 HBD |
percent_hbd | 10,000 |
post_id | 72,439,974 |
net_rshares | 81,588,865,587 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
kabir88 | 0 | 81,588,865,587 | 100% |
There is no exclusiveness for steemit.com. It is a simple dapp which interacts with the blockchain like any other dapp (d.tube, steepshot, busy) and they have no more rights to interact with the steem blockchain. The Hardfork introduced RCยดs which are a system wide upgrade. Every dapp needs to deal with the Resource Credits now.
author | geronimo |
---|---|
permlink | re-bashadow-re-geronimo-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181001t220218492z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 22:02:18 |
last_update | 2018-10-01 22:02:18 |
depth | 4 |
children | 1 |
last_payout | 2018-10-08 22:02:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.112 HBD |
curator_payout_value | 0.037 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 330 |
author_reputation | 2,923,721,121,912 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,440,052 |
net_rshares | 77,465,447,151 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
stimialiti | 0 | -2,497,450,850 | -100% | ||
kabir88 | 0 | 79,962,898,001 | 100% |
That sounds like a terrible idea. Unless people can eventually use the network however they want, it's all a waste of time. The future is not a BBC, in fact, the future probably looks more like Twitter/Facebook/Snapchat/Vine than a 10 000 word BLOG The most valuable content for on STEEM so far has been short. Every "high quality" post I've found is plagued by long-winded tl;dr'ness that only makes sense to steemit curation teams and completely misses the mark in terms of internet view ability and value. My 2c: the same message, conveyed in the least words possible, is way more valuable than the same message with all sorts of word-sugaring. We're already dealing with 10's of thousands of people who actually read over their posts and look at how they can make it longer for steemit, which is totally nonsense since to make a more valuable post you should normally try and condense it without losing info. A sad state of affairs and one that it looks like these decisions might drive deeper into our psychology if we're not careful.
author | lanmower |
---|---|
permlink | re-bashadow-re-geronimo-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181002t081202122z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-02 08:12:03 |
last_update | 2018-10-02 08:12:03 |
depth | 4 |
children | 0 |
last_payout | 2018-10-09 08:12:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.018 HBD |
curator_payout_value | 0.005 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,044 |
author_reputation | -4,369,177,824,692 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 72,465,052 |
net_rshares | 12,869,760,205 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
geronimo | 0 | 12,869,760,205 | 100% |
Posts and comments are almost identical from the perspective of the blockchain. Each is a transaction that is being submitted and that costs are almost the same. In some ways posts have more cost (they are usually larger) and for other technical reasons, with the same content, comments can have slightly higher cost. Trying to put timers on accounts as a mechanism to control abuse does not work. The abusers will set up multiple accounts and round-robin between then to evade the limit. At the same time, responsible non-abusing users won't do this and will be the ones whose experience is made worse by the limits (which is exactly what we saw with the previous 30 second limit on comments).
author | smooth |
---|---|
permlink | re-bashadow-re-steemitblog-hf20-update-operations-stable-20181001t220142400z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-01 22:01:48 |
last_update | 2018-10-01 22:01:48 |
depth | 2 |
children | 2 |
last_payout | 2018-10-08 22:01:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.037 HBD |
curator_payout_value | 0.010 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 696 |
author_reputation | 253,602,537,834,068 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,440,029 |
net_rshares | 26,469,344,782 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
whatsup | 0 | 18,466,733,789 | 5% | ||
lextenebris | 0 | 8,002,610,993 | 33% |
I did not realize time limits had been tried before. I know at one time there was a time limit you need to wait 20 seconds before voting, but I was not sure about for comments or posting.
author | bashadow |
---|---|
permlink | re-smooth-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181002t014221169z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-02 01:42:21 |
last_update | 2018-10-02 01:42:21 |
depth | 3 |
children | 1 |
last_payout | 2018-10-09 01:42:21 |
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 | 187 |
author_reputation | 100,388,692,638,882 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,448,614 |
net_rshares | 0 |
It was 3 seconds for voting, 20 seconds for commenting, 5 minutes for posting.
author | acidyo |
---|---|
permlink | re-bashadow-re-smooth-re-bashadow-re-steemitblog-hf20-update-operations-stable-20181002t032424967z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-10-02 03:24:27 |
last_update | 2018-10-02 03:24:27 |
depth | 4 |
children | 0 |
last_payout | 2018-10-09 03:24:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.048 HBD |
curator_payout_value | 0.015 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 78 |
author_reputation | 3,364,310,550,299,820 |
root_title | "HF20 Update: Operations Stable" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 72,452,868 |
net_rshares | 33,999,771,212 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
phoneinf | 0 | 33,999,771,212 | 24% |