create account

RE: Sad, but not yet defeated. by josephsavage

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @dreemsteem/sad-but-not-yet-defeated

· @josephsavage ·
$0.27
I wonder how feasible it would be for witnesses to set reward split levels in their configurations. Then the actual division at payout could be a moving 7 day average of configs assigned to each block. That would allow for each witness to target specific levels, justify their targets, and adapt as the community adapts.

There are tons of other components that work this way (like the 3.5 day average feed price used to calculate the portion of payout going to SBD) so the technical hurdles can't be too difficult.
👍  , , , ,
properties (23)
authorjosephsavage
permlinkre-dreemsteem-sad-but-not-yet-defeated-20190628t151711982z
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steempeak/1.13.5"}
created2019-06-28 15:17:12
last_update2019-06-28 15:17:12
depth1
children10
last_payout2019-07-05 15:17:12
cashout_time1969-12-31 23:59:59
total_payout_value0.208 HBD
curator_payout_value0.065 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length515
author_reputation40,260,007,396,591
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,470,261
net_rshares559,190,770,187
author_curate_reward""
vote details (5)
@bengy ·
$0.03
This sounds like a good middle ground compromise! 
👍  ,
properties (23)
authorbengy
permlinkre-josephsavage-re-dreemsteem-sad-but-not-yet-defeated-20190628t152130415z
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steempeak/1.13.5"}
created2019-06-28 15:21:33
last_update2019-06-28 15:21:33
depth2
children1
last_payout2019-07-05 15:21:33
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.006 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length50
author_reputation1,236,660,808,483,139
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,470,399
net_rshares55,640,663,401
author_curate_reward""
vote details (2)
@dreemsteem ·
there are many!  let's take the time to flesh this out and SEE who it hurts before just jumping into a decision that initially hurts so many small accounts (the current 50/50)

this is a discussion that DESERVES to be handled alone and handled right.  NOT quick and risky!
👍  
properties (23)
authordreemsteem
permlinkpttery
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steemit/0.1"}
created2019-06-28 15:24:03
last_update2019-06-28 15:24:03
depth3
children0
last_payout2019-07-05 15:24:03
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length272
author_reputation379,399,022,506,342
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,470,515
net_rshares5,840,404,290
author_curate_reward""
vote details (1)
@dreemsteem ·
I think there are many ways to tackle this - but the point is... we can't adjust it if it just gets voted on lumped into a yes/no deal.   This is TOO big of a discussion and there are SO many options that take us in a new direction WITHOUT burning the house down in one swift move.  I love that your comment immediately brought in another suggestion.  It's proof that if we put our minds together - there IS a compromise.

they need to take it off the hardfork so it can be a much more open and varied discusssion.
👍  
properties (23)
authordreemsteem
permlinkpttenl
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steemit/0.1"}
created2019-06-28 15:21:24
last_update2019-06-28 15:21:24
depth2
children0
last_payout2019-07-05 15:21:24
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length514
author_reputation379,399,022,506,342
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,470,395
net_rshares6,083,089,048
author_curate_reward""
vote details (1)
@shadowspub ·
why not a slider or setting for content creators to set what they are offering curators?

the platform will find its balancewith the give and take between the two groups in order for each to grow. When a content creator sets their rate too high in relation to the quality of their work, the curators wont be upvoting and the creator will need to rethink their rate.
properties (22)
authorshadowspub
permlinkpttwq4
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steemit/0.1"}
created2019-06-28 21:51:42
last_update2019-06-28 21:51:42
depth2
children6
last_payout2019-07-05 21:51:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length365
author_reputation624,936,964,368,595
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,485,929
net_rshares0
@josephsavage · (edited)
$0.20
That's an order of magnitude more complex from a technical perspective.

It would also require supporting development from every front-end and voting service running on Steem.
👍  ,
properties (23)
authorjosephsavage
permlinkre-shadowspub-pttwq4-20190628t215629345z
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steempeak/1.13.5"}
created2019-06-28 21:56:30
last_update2019-06-28 21:57:48
depth3
children5
last_payout2019-07-05 21:56:30
cashout_time1969-12-31 23:59:59
total_payout_value0.150 HBD
curator_payout_value0.048 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length175
author_reputation40,260,007,396,591
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,486,142
net_rshares408,934,267,208
author_curate_reward""
vote details (2)
@shadowspub ·
it is.. not impossible though. It happens elsewhere .. Choon comes to mind.
👍  
properties (23)
authorshadowspub
permlinkpttx16
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steemit/0.1"}
created2019-06-28 21:58:18
last_update2019-06-28 21:58:18
depth4
children0
last_payout2019-07-05 21:58:18
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length75
author_reputation624,936,964,368,595
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,486,215
net_rshares0
author_curate_reward""
vote details (1)
@tcpolymath ·
$0.03
You can already do this without too much trouble as long as the number is more than 25%. If you removed mandatory curation from the blockchain side I could spin up the back end of user-selected curation in a day or two. Somebody else would have to do the interface.
👍  , ,
properties (23)
authortcpolymath
permlinkre-josephsavage-re-shadowspub-pttwq4-20190629t031159375z
categoryhardfork
json_metadata{"tags":["hardfork"],"app":"steempeak/1.13.5"}
created2019-06-29 03:12:00
last_update2019-06-29 03:12:00
depth4
children3
last_payout2019-07-06 03:12:00
cashout_time1969-12-31 23:59:59
total_payout_value0.024 HBD
curator_payout_value0.007 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length265
author_reputation72,516,729,960,969
root_title"Sad, but not yet defeated."
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id87,498,304
net_rshares68,044,799,230
author_curate_reward""
vote details (3)