RE: Guidance needed: toward development of a ‘good bot’ (to aid account holders who want to prioritize ‘ecosystem growth’ over ‘individual profits’)

avatar
(Edited)

You are viewing a single comment's thread:

I think all you said is already possible on hive.vote if someone really wants to do that (prioritizing and blacklist/whitelist is not possible yet). I know some people set their votes like after 24 hours on hive.vote to support early voters but it's rare.

Anyway, hive.vote is not open source but there were some open source voting bots in the past. I don't remember any right now.

0
0
0.000
4 comments
avatar

Thanks for the info about hive.vote.

My primary interest here is setting it up so that those who actively and willingly choose to forego early-auto-voting curation rewards in order to avoid corrupting the manual curation process can be readily recognized for doing so.

Would you have any interest in working with me to add that capability to hive.vote? If so, feel free to DM me via OpenHive.Chat or Discord.

0
0
0.000
Reply
avatar

Sorry, wasn't around for a few days.
Can you explain what exactly to be added?

0
0
0.000
Reply
avatar

@mahdiyari, thanks for the reply!

I have registered for Hive.vote and explored its functionality.

It looks like you already have all the initial capabilities I was hoping for.

What I would like to add is an ‘opt-in’ for delayed autovoting and also an ‘opt-in’ for public recognition.

These could be added to the dashboard, right after the “Selfvote” option, with the following code change:

  • Users who opt-in for delayed autovoting will have their “fanbase” and “curation trail” wait times over-ridden to be 3,600 minutes (2.5 days).
    • (NOTE: The current max wait time is 1,440 minutes (1 day); if that is because Hive.vote only searches the last 24 hours worth of posts, then I guess the ‘over-ride’ time should be 1,440 instead of 3,600).

Then, if you could provide me with a weekly list of accounts that have opted in both for delayed autovoting and public recognition, I can write code to pull the voting histories for each of those accounts, identify the Hive.vote autovotes, and calculate the curation rewards each account sacrificed by choosing to delay their autovotes.

I will then periodically (e.g. weekly) publish a list of those accounts that chose delayed autovoting and the amount of curation rewards they sacrificed by doing so.

@arcange has agreed to help me learn the ropes with HiveSQL, so I can pull the necessary data from the blockchain to accomplish that task.

0
0
0.000
Reply
avatar

In the coming HF25, curation rewards will probably get reduced to somewhere between 10% to 25% (it's not decided yet). So I think it might be a waste of resources to work on adding something which will lose interest.

Sorry, I can't help with this.

0
0
0.000
Reply