I didn't specify it, but if any of the accounts listed in the 'CURATORS' section has already voted on the post, the bot will skip it and display a message in the console to notify you. No new vote will be cast.
It's this part of the code

source: https://gitlab.com/beblurt/blurt-voting-trail-bot/-/blob/main/src/index.ts?ref_type=heads#L141
it would be nice if the bot could recognize main posts and comments, then we could vote on comments with less power
Great idea 👍 I'm a little bit sick since yesterday, I'll make the change tomorrow I think and I let you know.
Hi. Yesterday and today we had a lot of problems with Blurt nodes. Blurtalam and blurtblog went down many times. I thought it might have something to do with the bot and turned it off. Everything came back to normal. Is it just a coincidence?
For the past few days, the three main RPC nodes of Blurt have been overloaded and crashing regularly. Since Blurtalam doesn't have its own RPC node, it is also affected by the outages. Only BeBlurt has its own RPC node.
Currently, a blockchain replay is underway on the three main RPC nodes. While waiting for them to come back up (as this process takes several hours), I have set up a temporary RPC node to assist in ensuring that Blurt.blog and Blurtalam can continue to function.
I've started bot again. For some reason this command didn't work for me - pm2 start pm2-ecosystem.config. I'm using pm2 start npm -- start instead. Looks like everything works fine but is that ok?
Hi @mariuszkarowski, sorry, I've been sick for a few days now, which has caused me to fall behind on various ongoing tasks. Regarding the
pm2 start pm2-ecosystem.config.js
command, its purpose is to add the program to PM2 using an Ecosystem File and initiate its execution. I'll review this as soon as I am able to. Additionally, I plan to make the modification to distinguish between posts and comments.Hi @mariuszkarowski, Blurt Voting Trail Bot updated to version 1.1.2 with differentiated upvotes for posts and comments.
You can do a
git pull
in the directory to update and you will have to modify yourconfig.json
file to replaceTYPE
&VALUE
byPOST_TYPE
,POST_VALUE
,COMMENT_TYPE
, andCOMMENT_VALUE
parametersexample:
And I fixed the pm2 issue too (my mistake, I forgot it was in ESM so the extension is
.cjs
and not.js
). To start with PM2, the command is:I've updated the documentation: https://gitlab.com/beblurt/blurt-voting-trail-bot
Great update. If I may suggest something: it would be nice to have a "no vote" option for posts that has been voted by vote trading services like upvu, tomoyan, etc... because users of these bots have a big return on their BLURT Power anyway.
Hi @mariuszkarowski, Blurt Voting Trail Bot updated to version 1.1.4 with
EXCLUDED_VOTERS
list to add in the config file. if an account is present in theEXCLUDED_VOTERS
list and has upvoted for the post, the upvote is skipped.I've updated the documentation: https://gitlab.com/beblurt/blurt-voting-trail-bot
testing https://blurt.blog/curation/@onchain-curator/occ-s-art-of-curation-or-5th-august-2023
https://ecosynthesizer.com/blurt/blk/31776574
error

53 X 0.7 = 37.1