In this post, I introduced the bot hive-archeology-bot that is a personal bot that allows the user to vote on high quality timeless HIVE posts as if (s)he was voting on posts still in their initial 7 day time window.
The bot runs in the background, monitors for votes by its master, and then creates and votes on a proxy comment that is a votable placeholder for the actual post.
Five $HIVE for random bot user (x7)
Before we age getting to the main subject of this post, a little detour. I'm giving away 35 HIVE to users of the personal bot, or to be precise, seven times five HIVE. Right now as far as I've seen, two people have installed and used the bot, and I would really like some more users. I hope this post on installing it on a NAS will help with that, but I'm also adding a tiny insentive.
In the coming seven days, or until the 35 HIVE runs out, I'm giving away 5 HIVE to a random person who I can see used the bot to up-vote timeless content that day.
- Every day, until the 35 HIVE runs out, if there are eligible up-votes made with the bot, a random up-voter will be selected and receive 5 HIVE
- An eligible up-vote should have a value of at least 0.02 HBD
- A winner can not make eligible up-vote until at least two other people have won since his/her last win.
Installing the personal bot on your (QNAP) NAS
In the previous post we showed how you can run the hive-archeology-bot on your PC. The drawback of this is that you probably don't want to have it running on your laptop 24/7, and you don't want to think about it running.
In this post we are going to look at how you can run this same personal bot on your NAS. In this walkthrough we use a QNAP nas, but if you have a synology, the setup shouldn't be all that much different.
The first thing we need to do, after logging into the QNAP is to start the Container Station.
Next we select Images in the left menu:
Now at the top right, we see a button named Pull. Push that button.
There is a docker image available on docker hub under pibara/hive-archeology-bot. Fill that out in teh Image Name box and press Pull
Now be patient, and in a few minutes the image appears in the list
The next step is to push the plus sign under Actions to create a new container.
Leave everything as it is here, what we need to change is under Advanced Settings.
We are going to add two environment variables to make things run.
- HIVE_ARCHEOLOGY_USER : Your HIVE account
- HIVE_ARCHEOLOGY_WIF : The WIF of your posting key private key.
That's it, press create and the hive-archeology-bot will be running when ever your NAS is running, what should normally be always.
Now, even if you are on the road, upvoting HIVE posts from your phone or tablet, your personal bot will be there to transparently turn up-votes on paid-out posts into upvoted proxy-commentts like this:
The comment is a bit more informative now, hopefully being a little less inviting for accidental self-up-votes.
That's it for this post. There are some improvements to the bot that I'll talk about in another post soon. For now, give the bot a try and find ad reward some timeless high-quality content on HIVE.
really cool idea; maybe the major front ends could implement it in a more accessible way? @peakd
@tipu curate
One can easily leave a comment under an older post and upvote the response. Money goes to the same place plus there's no middleman skimming profits. And if there's no response, then you know you're not upvoting or supporting a dead account. Even if it took three months to get a response, one can still support that old post by upvoting the author's response when/if it arrives.
Would it be possible to include a feature disallowing the ability to support a "dead account?" Sure the post might be great but if the author is gone for reasons including losing their keys, supporting them is throwing stake into the void. People run into the same issue tipping old work. You don't throw a dollar on the street where a busker once performed because they might be there again tomorrow to pick it up.
Sure, if you can make an issue on github and make description of what constitutes a dead account.
Think there are two ways to make a feature like this:
The second one is simplest, but will wrongly mark an account as old if the account for example stopped voting and posting but still claims beneficiary rewards.
The first one is more robust, but might need more than N items of history to work through bacause the result includes both sides of multi-party operations, for example fund transfer to the account or a delegation being retracted.
If you can write a solid spec of which one of these two is more desireable, and in the case of #1, fully specify the desired runthrough of the API response, I'll implement it in the next maintenance round.
Unfortunately I don't do all that fancy shmancy dev stuff so I can't be much help to you in that department. If I could, I would.
PeakD indicates when an account was "last active." Perhaps "dead" is the wrong word to use so I'll replace that with "inactive." If an account is inactive for two years, my guess would be supporting it could be wasteful. Even one year there's a strong chance they're not coming back, but they might. There are thousands of posts published by accounts that have not been active on Hive.
If one wanted to be really fancy, the vote could be processed once the inactive account becomes active.
Again, I can't help come up with a working solution. I'm sure you can see how it could be a problem. I suppose those voting should be paying attention to a little more than just the post when they decide to support older work.
Created an issue, could you check if it looks OK like this/
https://github.com/pibara/hive-archeology/issues/1
Looks fine to me.
If this method of earning beyond 7 days becomes popular, perhaps people will hear about it, and return. Especially encouraged to return if signs of activity help one qualify for a chance at those added rewards.
I agree with another commentator here recommending something like this system come standard with frontends. There's a shortage of actual paying consumers but providing them with more variety of products (content) to support could help encourage them to show up as well, if everything is straightforward and easy to accomplish.
We'll see.
Thanks for your time.
To illustrate, if I look at @nonameslefttouse with #1, and look at the last 1000 operations, apart from votes by you and posts/comments by you (and matching rewards and claims), I get:
Congratulations @pibara! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
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 our last posts:
Nice work. I have an appeal which I just tweeted to you and also @ausbitbank
Your idea is probably not compatible with the original content concept on HIVE, and thus would likely be considered abuse by many. Realize that you'd be posting other peoples content and harvesting rewards from it.
99% of content will be mine! @dexterdev 1% will be from other users as of now. Can't we link their accounts to HIVE somehow when they post it?
This is interesting