You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
--community : Auto up-vote new Hive Archaeology proxy comments with 25% whren VP reaches 99.5% or higher.
--community-pct [PCT] : Auto up-vote new Hive Archaeology proxy comments with PCT% when VP reaches 99.5% or higher.
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:
--community-blacklist [LISTNAME] : Set a blacklist of accounts whose proxy posts never to upvote
--community-tag-blacklist [LISTNAME] : Set a blacklist of post tags for what proxy posts never should get upvoted
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: