I'm sure there are a lot of pros that will come out of this to outweigh the few cons it may be used as, one of them being a bid bot. Either way, it was inevitable for a service like this to exist at some point and depending on how we use it it can go a long way. Best case scenario it will encourage more manual curation and better and longer content instead of accounts throwing 2.5% votes all around. :p
Best case scenario it will encourage more manual curation and better and longer content instead of accounts throwing 2.5% votes all around. :p
Guess why they are doing it. Btw, I see two different ways to fix the problem:
rid off of the curation curves and all penalties for early/late voting and low post payout
or
let them continue this crazy and toxic race for curation awards, which doesn't have anything to do with the real manual curation and create a Super Power for those who want to curate manually. This Super Power would be staked for 13 month and will always get back 50% from vote value
Thing is that this race ends at some point, it's game theory that has been discussed quite a few times. Say a very popular and consistent author would start seeing front-runners front-running the front-runners until the very early votes are so early that the penalty doesn't make it worth the returns.
Hmm, your 2nd idea would discourage content discovery which is why the curve exists in the first place. The problem is people get lazy and not many check the "new" of all posts, with communities it is getting better as more curators are focusing on their own communities and being able to not miss many posts. This is also why we want to focus on bringing more niche communities up the ranks with our curation efforts of OCD so that newcomers that join don't post outside of communities but have a big variety to choose from early on and find their "place".
@reward.app does balance out the early voting a little bit and we could experiment some more with how the "extra" curation rewards are calculated to discourage early voters a bit more. I think with the EIP but with 25/75 this experiment would've worked better as it would've given us a bigger range to work with to switch up how we distribute curation but that's out of our control right now.
If anything it will add some more simulations and testing to new parameters to maybe help in a future hardfork if we come up with better solutions for content discovery. There's a lot of other pros to it and that's a big reason I decided to go forward with it but I understand the skepticism at first glance.
What I'm saying is: I just want to read the posts, upvote the ones I like and get back 50% from my vote value.
Why autovoters who don't even read posts, do profit from my investment? Should I invest more in Hive, once I know this fact?
You are trying to fix the issue without any changes to blockchain code. I understand your intentions. I wish you good luck, but it will be hard to achieve your goals
Frankly speaking a business model on broken code. Curation curves are complex for a normal "facebook"+twitter user whom they want to onboard here.
And I think very few has has interest in promoting the manual curation and every effort is done to penalize the authors only though claimed backbone of a blogging system but I doubt in practice.
I'm sure there are a lot of pros that will come out of this to outweigh the few cons it may be used as, one of them being a bid bot. Either way, it was inevitable for a service like this to exist at some point and depending on how we use it it can go a long way. Best case scenario it will encourage more manual curation and better and longer content instead of accounts throwing 2.5% votes all around. :p
Guess why they are doing it. Btw, I see two different ways to fix the problem:
or
Thing is that this race ends at some point, it's game theory that has been discussed quite a few times. Say a very popular and consistent author would start seeing front-runners front-running the front-runners until the very early votes are so early that the penalty doesn't make it worth the returns.
Hmm, your 2nd idea would discourage content discovery which is why the curve exists in the first place. The problem is people get lazy and not many check the "new" of all posts, with communities it is getting better as more curators are focusing on their own communities and being able to not miss many posts. This is also why we want to focus on bringing more niche communities up the ranks with our curation efforts of OCD so that newcomers that join don't post outside of communities but have a big variety to choose from early on and find their "place".
@reward.app does balance out the early voting a little bit and we could experiment some more with how the "extra" curation rewards are calculated to discourage early voters a bit more. I think with the EIP but with 25/75 this experiment would've worked better as it would've given us a bigger range to work with to switch up how we distribute curation but that's out of our control right now.
If anything it will add some more simulations and testing to new parameters to maybe help in a future hardfork if we come up with better solutions for content discovery. There's a lot of other pros to it and that's a big reason I decided to go forward with it but I understand the skepticism at first glance.
What I'm saying is: I just want to read the posts, upvote the ones I like and get back 50% from my vote value.
Why autovoters who don't even read posts, do profit from my investment? Should I invest more in Hive, once I know this fact?
You are trying to fix the issue without any changes to blockchain code. I understand your intentions. I wish you good luck, but it will be hard to achieve your goals
Frankly speaking a business model on broken code. Curation curves are complex for a normal "facebook"+twitter user whom they want to onboard here.
And I think very few has has interest in promoting the manual curation and every effort is done to penalize the authors only though claimed backbone of a blogging system but I doubt in practice.
Yeah, in curation area we are still running Ned's code. Let's hope HMT won't make same mistake