RE: Scalability, Content Quality and Centralization - An open discussion on an incentivized downvote system by owdy

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @arcurus/re-owdy-re-williambanks-re-owdy-scalability-content-quality-and-centralization-an-open-discussion-on-an-incentivized-downvote-system-20160812t102405479z

steemit · @owdy · Aug 12 '16 (edited)

>In away it would be like a prediction market

Exactly!


>I would suggest to allow 3 different kind of votes:
...

Yep! There's definitely something that could be done with voting weight.  It's already there in the background on Steem, just not on Steemit, so integrating that shouldn't be too difficult. 

I agree about your second point, but I don't see it as a real solution to the problem as Steemit scales up. The number of spots on trending is just too limited for that implementation to have a large impact. Even right now, we're talking about 4000 posts/day, there's just no way a lottery system can cycle through enough of those to make a major difference. - What do you think?

properties (22)

`author`	owdy
`permlink`	re-arcurus-re-owdy-re-williambanks-re-owdy-scalability-content-quality-and-centralization-an-open-discussion-on-an-incentivized-downvote-system-20160812t130913098z
`category`	steemit
`json_metadata`	{"tags":["steemit"]}
`created`	2016-08-12 13:09:15
`last_update`	2016-08-12 13:10:06
`depth`	4
`children`	2
`last_payout`	2016-09-09 13:28:03
`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`	687
`author_reputation`	3,152,666,625,062
`root_title`	"Scalability, Content Quality and Centralization - An open discussion on an incentivized downvote system"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	764,398
`net_rshares`	0

@arcurus · Aug 12 '16

a the lottery system from trending topics can scale up perfectly, because the articles are chosen for every user each time he reloads the site. So it can even scale with billions of users and articles :)

properties (22)

`author`	arcurus
`permlink`	re-owdy-re-arcurus-re-owdy-re-williambanks-re-owdy-scalability-content-quality-and-centralization-an-open-discussion-on-an-incentivized-downvote-system-20160812t135749028z
`category`	steemit
`json_metadata`	{"tags":["steemit"]}
`created`	2016-08-12 13:57:48
`last_update`	2016-08-12 13:57:48
`depth`	5
`children`	0
`last_payout`	2016-09-09 13:28:03
`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`	203
`author_reputation`	549,553,053,579
`root_title`	"Scalability, Content Quality and Centralization - An open discussion on an incentivized downvote system"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	765,013
`net_rshares`	0

@owdy · Aug 13 '16

@arcurus You're right! I misunderstood the concept, if it's done on an individual basis it could certainly work. I like the idea and, right now, I can't really think of a better way to easily address visibility issues.

properties (22)