RE: RANT Post - Auto Curation sucks - Hot Take
You are viewing a single comment's thread:
The vacation mode sounds interesting and it feels like hive.vote should have an option where only if your voting power is getting close to 100% will it follow one or many trails or automatically vote on some posts/comments that are always there and active, think like hbd.funder comments that benefit us all and don't go to a central entity that personally benefits from the rewards.
I don't know however how possible it is to create such an option as it may be costly in terms of API calls for the service to know when you hit 100% or even 99.9% to start casting trail/autovotes to save you from "wasting" mana and in tern curation rewards. This would however let you curate manually more efficiently as you stated, you would find yourself more often at 98-100% vp so your manual vote then would be worth as much as it can and you wouldn't have to worry about having to vote 10+ posts every day if you're fully manual.
Maybe @mahdiyari who's behind hive.vote could weigh in on the idea.
ohh I do like that too. Yeah I mean I get Curation is a MASSIVE part of Hive blogging and such but I don't know. A part of me is just wanting more real use interaction and comments/replies and not just the auto upvotes.
Which is weird cause autovotes mean more HP/HBD for me and the voters but.. yeah idk
I think autovoters trailing ocdb are mostly afk so better that than letting it sit idly, best would of course be delegations as it would just be one account voting and not confuse newcomers that x amount of people saw the post like they're used to with likes and upvotes in 1 account 1 vote systems.
TRUE.. that would be much better
Maybe I got it wrong, but you can already do something similar by setting an "Upvote Mana threshold":
In this example above - which is taken from my dashboard on hive.vote - I set a threshold of 95%, so my account follows the curation trails I chose only when my upvoting power is more than 95%, and pause when it's below that value.
I have activated a few curation trails (with a small voting weight, between 5% and 15%, for each one), so my voting power never touches 100%, but also never goes below 94.xx%.
@cherokee4life I'm afraid that something like that would stop a lot of people from activating an option like the one you described: if you are managing your voting power so well and responsibly, almost always voting manually, maybe there's no need to decline the curation rewards you earn while on vacation!
I thought the threshold worked the other way, if you drop under it it will stop voting after your trail. Isn't that why your many is 96.xx% in your screenshot when you have the threshold at 95%?
Yep, but this isn't what you were looking for?
Because with the threshold hive.vote (in my case) only casts a vote and follows the curation trails I chose when my voting power is getting close to 100% (i.e. is above 95%).
But I may be missing what you are saying, so sorry if this doesn't make sense 😅
I don't know what it does exactly, I thought the threshold was a stop limit such as when your voting power gets to it (95% in your example) will it stop voting, not the other way - start voting if vp gets above 95%. But I may be wrong, don't use hive.vote much other than trailing ocd with ocdb and ocd-witness.
Isn't this the same thing?
So if I set a threshold of 99%, hive.vote only casts votes when my vp is close to 100%.
And if I vote manually and, let's say, bring my voting power down to 89%, hive.vote stops and wait for it to recharge to 99% (which might never happen if I keep curating manually, but may come in handy if I'm on vacation, like in the example made by @cherokee4life).
You know.. to be honest now that I read your reply. I am not sure I even knew how hive.vote worked cause I thought it was that it would vote with a set weight until your Voting Power got down to a certain % but now I am not sure lol
At this point I'm more confused than you and @acidyo 🤣
This is right! Let's say you activate a curation trail following @acidyo's votes and you set a threshold of 97%.
You just signed on Hive and have some HP, so your voting power is at 100%.
@acidyo casts a vote.
hive.vote detects this vote, checks if your voting power is above the threshold (it is, because you are at 100%) and then casts a vote with your account.
Now your voting power is, let's say, 98%.
@acidyo votes again and hive.vote repeats the same procedure (detects the vote, checks your voting power, sees that it's above 97%, casts a vote).
Your voting power is 96% now.
@acidyo casts again a vote.
And this time things go a little different: hive.vote detects the vote, checks your voting power, sees that is below 97% (you are at 96%), so it doesn't cast a vote. The curation trail is paused.
To me it looks like we are all saying the same thing, so I'm clearly not understanding what you both are saying... sorry about that! There's surely something I'm missing 😅
lol honestly it is my biggest pet peeve with Hive in general though where there is not as much Concrete information readily available to the new user. Things change and there is no 1 central location for ALL up to date info.
But yeah maybe we all are saying the same thing? idk anymore its been a busy morning haha
yeah, it's one of our major issues: on Hive you can do thousands of things, but there's little to no explanations on how to do them. Most of the time you have to try or hope to find that random post talking about something you had no idea you could do... Having a site with clear and updated instructions and tutorials would be great! Maybe this is something we should do, one day or the other (unless it already exists and I'm not aware of it!).