Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

100% VP auto up-vote of Hive-Archaeology proxy comments #2

Open
pibara opened this issue Jun 18, 2023 · 1 comment
Open

100% VP auto up-vote of Hive-Archaeology proxy comments #2

pibara opened this issue Jun 18, 2023 · 1 comment

Comments

@pibara
Copy link
Owner

pibara commented Jun 18, 2023

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
@pibara
Copy link
Owner Author

pibara commented Jul 1, 2023

Won't implement the blacklist as settable, we use naming conventions instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant