HiveVote
Found out about HiveVote from this Rising Star post. How this works is you follow a curator using the curator trail menu and you automatically upvote the post they just upvoted. It is like a copy service for upvotes. You just need to set the parameter and let it do the rest. The link from above has some nice explanation about the settings. Please also make sure the curator you're following does not upvote low quality posts.
This can also work for someone you follow, upvote their post as soon at it is published. I like this service compared to delegation as the Hive Power is still on your account so replenishment of resource credit is never an issue for me. HiveVote have other things it can do but I think these two are the most useful. Thank you @mahdiyari, you made my life easier.
Self Vote
While looking through HiveVote's dashboard, I noticed the SelfVote option and it is set to true as default. I am not familiar if this is an oversight or what since there are a few unwritten rules on Hive. Found this post by @bozz where he asks for the unwritten rules and collated it. From this, it looks like self voting is an accepted practice as long as you don't upvote your own comment.
Self Vote Statistics
My curiousity piqued, I used HiveSQL to find out how many authors upvoted their own post.
Below is the number of authors who self voted their own post at least once. Based on this, it looks like less and less author are self voting their own post.
| No of Authors | Year |
|---|---|
| 11,676 | 2022 |
| 18,915 | 2021 |
| 22,207 | 2020 |
| 59,229 | 2019 |
| 259,513 | 2018 |
How about you? What's your take on self voting on own post? Let me know in the comments.
Thank you for reading.
Image screenshot from MS SQL SMS.
Congratulations @maakue! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):
Your next target is to reach 800 replies.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out the last post from @hivebuzz:
Yay! 🤗
Your content has been boosted with Ecency Points, by @maakue.
Use Ecency daily to boost your growth on platform!
Support Ecency
Vote for new Proposal
Delegate HP and earn more
FYI, the NOLOCK hint is no more required on HiveSQL queries ;)
The TxVotes table is quite big.
For better performances and to lower load on the server , it's better to use a time range in your WHERE clause (ex:
timestamp >= '2018-01-01' AND timestamp < '2019-01-01')instead ofYEAR(timestamp) = 2018.This will allow the server to use the timestamp index and avoid it to execute the YEAR() function on every row.
Finally, you may take into account the weight of the vote. If it is negative, it's a downvote, not a self-[up]vote.
That being said, I doubt anyone has ever downvoted themselves 😂
Thanks for the tips.
You're welcome.
BTW, as you use it, may I ask you to support the HiveSQL proposal? That would be much appreciated.
You can do it on Peakd, ecency,
Thank you!
Done. Sorry I missed that.
Thank you for your support, really appreciate it! 👍