At this point I'm more confused than you and @acidyo 🤣
it would vote with a set weight until your Voting Power got down to a certain %
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 😅
RE: RANT Post - Auto Curation sucks - Hot Take