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.
I think there might be an issue with potential target audience for such tool. It might be too complex for beginners, while power users would rather use their own solutions.
Its just:
Not sure how I could make it any less complex.
I'm running a little experiment now with leaving a proxy comment without up-voting with my own bot instance, going to look what it comments on for a day to see if that is a viable use-case.
!DHEDGE
Looks interesting, but couldn't you avoid all the requirements for others to host it themselves, and just change the setup so only one account ever needs to be used for this? Set it up so an account can be called in via comment command like the one above, your bot will create a reply with the beneficiaries set as desired, and the user can just upvote it to reward the content, while you collect your cut every time without worry....
I'm running a little experiment right now with leaving a proxy comment without up-voting with my own bot instance, going to look what it comments on for a day to see if that is a viable use-case.
If this option doesn't turn out, I'm contemplating either what you proposed, or a whitelist or blacklist added to the current experiment.
A nice whitelist option I like to use is whoever the bot account is following. You can have your bot pull following every so often and make a list from that. This will allow you to easily update your whitelist with the click of a button through your favorite front end.
How about having it run in a browser extension? May not be able to use python like that though.
Cool bot! I'm definitely going to check it out!
@captaincryptic
!lolz
It looks like it is possible...
lolztoken.com
But it folded.
Credit: reddit
@pibara, I sent you an $LOLZ on behalf of @lolztoken
(2/10)
Farm LOLZ tokens when you Delegate Hive or Hive Tokens.
Click to delegate: 10 - 20 - 50 - 100 HP
Hello! is nice to have such tools here to count on!
will be testing next days and give feedback ^_^
everyday we learn something new
keep going on Bro
I appreciate your efforts. Never really understood why the seven day cut-off was necessary.
Edit: Had to highlight and share in the irony... Your last post 'failed,' as you say, because there was only a small window of time for people to discover and potentially act upon it's contents 😁
Feature 7: Discord to comment bridge
As described in this tweet by @dexterdev, there are HIVE communities that consist of both a Discord server and a HIVE community.
It might be interesting as a feature for Hive Archaeology personal bot users to bridge Discord content to comments on a daily community post.
To not collide with HIVE proof of brain ethics, these posts and comments will have to be declined payout posts.
For this feature we define the following flags:
Next to this, other flags and env variables are going to be needed but we will first need to explore the discord API for figuring out ecactly which ones we need.
cool! But what is the issue with monetization of real valued content which is not spam? [late to the discussion]
The issue is with mapping discord users to HIVE users. If you run a bridge on your discord server, most of the discord content will be by other people of who the bot won't have a HIVE account to map it to.
Let us think something like this: The server has an account! and maybe ghost accounts of all users? Let the account(s) post and the rewards be decided by the server to the people in the server later or we convert(to discord bonuses) or keep the rewards(as it is in the ghost accounts)?
feature 2: Daily reports
Currently the Hive Archaeology based up-voting of old and timeless high quality content is a lonely task. This feature will only be usefull for users that run the bot 24/7, for example on their NAS. The idea of this feature is that we can let the bot generate a HIVE post once a day (at most) with a list of posts that were up-voted by the bot. This post will be done using a #hivearchaeology tag, so other Hive Archaeology users, but also just HIVE users willing o up-vote the proxy post can use it.
This feature will introduce the following flag:
Feature 3: 100% VP auto up-vote of Hive-Archaeology proxy comments
While running Hive Archaeology on your NAS or other system as your private bot, normally the bot only responds to your up-votes of old high quality posts. While manual personal up-votes are always better, when your VP is at 100% or just below, you don't want your voting power to go to waste.
This proposed feature we want the user to be able to run the Hive Archaeology Bot in a mode where at VP of 99.5% or more, the bot will start 25% (default) auto up-voting proxy comments created by other Hive Archaeology Bot users.
We define two flags:
When using one of these flags, by default all Hive Archaeology users are trusted but we need a way to blacklist.
For this you can set your own list:
Feature 4: CroupierBot features
In the distance past, the author of Hive Archaeology ran the Croupierbot on HIVE as a public service for verifiable random draws.
The idea was that anyone can invoke the bot to ask for a random draw that is based on the blockchain.
This proposed feature aims to ressurect the Croupierbot functionality in a distributed way. It is proposed that every Hive Archaeology bot is always a CroupierBot validator, and running the public service is optional using the following flag:
When the croupierbot is running enabled, everyone can ask it one of a number of commands by starting a comment with a mention of the account running the croupierbot followed by a command with command specific arguments. The initial verstion will only support the following command:
The first response to this will be the bot creating a custom JSON post meant for itself and peer validators. This custom JSON contains a structured version of the command and a near future block number and a link to the comment for responses.
When the block is published, the all the bots determine the winner of the lottery and post a response with the winner according to the custom JSON and the block used for entropy.
Feature 5: 100% VP auto up-vote of peer-curator curated posts
While running Hive Archaeology on your NAS or other system as your private bot, normally the bot only responds to your up-votes of old high quality posts. While manual personal up-votes are always better, when your VP is at 100% or just below, you don't want your voting power to go to waste.
This proposed feature we want the user to be able to run the Hive Archaeology Bot in a mode where at VP of 99.5% or more, the bot will start 25% (default) auto up-voting in-window posts curated by peer curators.
We define three flags:
By default all tags curated by peer curators in the list could end up getting up-voted, unless the following flag is specified:
Feature 6: 100% VP auto up-vote of peer-created posts
While running Hive Archaeology on your NAS or other system as your private bot, normally the bot only responds to your up-votes of old high quality posts. While manual personal up-votes are always better, when your VP is at 100% or just below, you don't want your voting power to go to waste.
This proposed feature we want the user to be able to run the Hive Archaeology Bot in a mode where at VP of 99.5% or more, the bot will start 25% (default) auto up-voting in-window posts created by peer post authors.
We define three flags:
By default all tags created by peer authors in the list could end up getting up-voted, unless the following flag is specified:
This post has been selected for upvote from our token accounts by @dhedge! Based on your tags you received upvotes from the following account(s):
- @dhedge.bonus
@dhedge has 3.0 vote calls left today.
Hold 10 or more DHEDGE to unlock daily dividends and gain access to upvote rounds on your posts. Hold 100 or more DHEDGE to unlock thread votes, and the ability to call our token curation accounts for other users! You can buy DHEDGE on Tribaldex or earn some daily by joining one of our many delegation pools at app.dhedge.cc.
The Hive.Pizza team manually curated this post.
Join us in Discord!
I have seen many people who upvote comments when the 7 day voting period is finished, this will help them a lot.
Congratulations @pibara! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 3000 comments.
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
STOPoops sorry I missed a lot. I am back after a chaos phase in life :)