Python Libraries: HIVE Voting BOT - Duplicate Account and New Account Fixes
88 comments
I mentioned to @livinguktaiwan that I had to adjust the bonus weights for BOT voting because I am struggling to use up my voting power.
I can set the BOT to run, and hours later, it’s still going and has not breached the level I set as a cut-off. Fewer people are posting, and the ones who pass the rigorous tests I put in place are fewer.
To put it simply..., these values are applied to whatever vote weight the BOT decides to give the author. So a vote of 10% could end up being somewhere between 14% and 19%. If the HIVE token decreases, then you will less $ value but more HIVE value.
It's free votes aka free money and nobody is interested, what’s wrong with everyone? If you get votes from @slobberchops NOW and they contain decimal points, then your post has been BOT voted.
You can see the this easily using HiveTasks. Whilst I would love to manually curate articles, there are not enough hours in the day, and running this twice or three times a day saves me a shitload of time.
Saturdays seem to be my BOT development days of late, I add some more code, up the version and test it with the debugmode variable set to True. I can then run it, without it voting for anyone, but the motions are all the same otherwise.

...'a section of the votees list. Anyone here is likely to get voted as of now as posts are a scarce commodity'...
I do get generated logs for each run, but this aspect is a little crap or was. Choosing a random name from a large list is all very well, but in a single run, the same name could be picked out several times.
I needed a temporary list creating and cross-referencing against to ensure the same name is not submitted to all the various checks I use on every account and post when picked.
Not a big deal, initialise it and then add it to the while loop within the account choosing part of the script. If the account name does not exist in votees_processed then the next line is executed.
The main function that accepts a returned integer value into the outofvpaccounts variable kicks off the voting routine, and when it returns the account is then added to votees_processed with the append method.
It works but it looks shit when ran! I don't have my eyes glued to the screen output, but do like things to be highlighted. Using no spacing and red text shows me @sooud has been picked twice and identifies this fix works.
Add a couple of line feeds, use AQUA and it's much easier to spot, especially when the text is racing up the screen.
The longer the script runs, and finds nothing to vote, the more frequently it will find a duplicate name, and if the votees list is large enough, in theory all the voting accounts should reach their thresholds first.
This is why I want the votees list to be LARGER (more of that at the end of this post).
I did a similar thing (when it comes to colours) when adding the KE ratio factor into the last version of the BOT, so could easily see if the account was a 'Leeching Arsehole'.
@unitmaster could well have been one of those, but this is due to expectations of HP vs Account age. Not everyone posts everyday and is super active and that's where the second check comes in. The fact this author is talking about 'Hive Growth' is even better.
4.82% is not a large vote, but I do like to spread the love, and @unitmaster's KE ratio is better than mine. Maybe I should add a extra bonus for level of KE. The lower, the bigger the bonus?
The logs are now better but not perfect at all.
31 accounts received a vote, not even close. It was actually 3. The reason being that 28 of the 31 eligible had already received a vote. Quite sad isn't it?
@patif2025 is a new account and should have received a vote but as this was the last account to be checked before all of them were low on VP, no vote was issued. In fact this account should have been bypassed as it is too new, which made me fix yet another bug.
the snarkycomment variable reveals the answer and this one won't get a vote until 90 days has elapsed. @patif2025 will need to be a little more patient, but is a whitelisted account (for now).
...'THE SLOBBERCHOPS WHITELIST'...
Would you like to be whitelisted and eligible for votes by me (and a bunch of other accounts?). Drop me a comment on this post, and I may add you (subject to account checks).
Twice or three times a day I manually run the BOT until the voting thresholds on all the accounts have been breached. You may get a vote, or you may be passed by.
A vote depends on passing the checks I have put in place, and if your name is randomly picked. There's nothing to lose, you get votes, could be small or large and I get curation rewards.
Do you like posting your Urbex content and photography for FREE on Facebook and YouTube? I like to get some form of reward for my work and every time I create I do just that. Take a look at The Urbex Community on HIVE.
If you want to keep creating for FREE then ignore what you are reading. If you want to be like me and gain something other than BUGGER ALL for your work then click here and learn about posting on the HIVE blockchain.
My Urban Exploration Tales can be found directly on the internet via my
Website: 'Tales of the Urban Explorer'.

If you found this article so invigorating that you are now a positively googly-eyed, drooling lunatic with dripping saliva or even if you liked it just a bit, then please upvote, comment, rehive, engage me or all of these things.

Comments