This is my 4th post on the subject of the Hive Archaeology Bot, your personal bot for up-voting timeless high quality content on the HIVE blockchain that is past its initial 7 day window of existence.
After the initial 7 day windows, there are three ways to still reward timeless content:
- Using the @peakd's tipping feature. It's a bit hidden, but you can tip[ the creator of a post with HIVE or HBD.
- Using @brianoflondon's V4V App to send a tip using lightning instead of HIVE, this is amazing for allowing non-HIVE-users to tip content.
- Using your own personal Hive Archaeology Bot
In my first post, I introduced the bot and showed how you can run it on your regular machine. In my second post I walked through how you can install the personal bot on your home QNAP NAS. The second post did very well and I was expecting some uptake, so in my third post I tried giving away 70 HIVE to random Hive Archaeology users, but to my disappointment I was the only user during the whole 10 days that my giveaway ran, so now I get to keep my 70 HIVE but I'm not happy about it.
My thought now, the bot must be missing some features, maybe if I implement a few of those, people will start using the Hive Archaeology bot on their own account, and my goal of making HIVE a more welcoming place to creators of more timeless content such as art, poetry, and like my own fiction, might still come a little closer.
So what I'm going to do in this post is list all the features that I think I could add to this bot to make it better and more attractive in use. Two of them were entered by HIVE users.
I'll start off with the list.
- Add flag to ignore upvotes posts by accounts that have been inactive for long: @nonameslefttouse
- Discord to comment bridge :@dexterdev
- Daily reports
- 100% VP auto up-vote of Hive-Archaeology proxy comments
- Croupierbot feature
- 100% VP auto up-vote of peer-curator curated posts
- 100% VP auto up-vote of peer-created posts
I want to try something new now. I'm going to write seven comments now describing the new options that I could implement next. And I'm going to ask you, the reader of this post no not (or not only) upvote this post but to just (or also) upvote one upto four of the seven options using the weight you feel appropriate.
If the bot gets some users, I'll eventually implement all of them, but if I implement the first few and there still is zero adoption, I won't waste more time on it after implementing the first few.