:-D True !INDEED :-) But I wouldn't feel it as being fair I'm afraid :-D
!PIZZA
You are viewing a single comment's thread from:
Sort: Trending
I don't think you should prevent other Hive users from tipping you with !INDEED tokens just because they will come from your INDEED bot. 🤯😅
In the sense of "giving back" you mean? The thing is that it would result in a net zero operation. I'm not sure even if the nodes would accept such transaction... Haven't tried it yet to be honest...
!ALIVE
The INDEED bot is what will send your personal Hive account INDEED tokens, not that the INDEED bot will tip itself. 😅
If a Hive user still wants to tip the INDEED bot itself with the INDEED token, maybe just make the bot say "thanks" and deduct 1 from the available tips of the user for the day. 😎
Good point! I've added it to my "things to consider to improve the bots"-list ;-)
!INDEED
!BBH
No matter how good those improvement ideas are, they would only be secondary to the bugs and issues of your bot. 🤓🧘♂️😅
!LOLZ
He was banned from the zoo.
Credit: reddit
@borniet, I sent you an $LOLZ on behalf of savvytester
(5/10)
Farm LOLZ tokens when you Delegate Hive or Hive Tokens.
Click to delegate: 10 - 20 - 50 - 100 HP
I haven't discovered bugs from the !INDEED bot, apart from occasionally not fulfilling valid IDD tipping commands. 🤔🤯😅
Thank you for keeping an eye on it ;-)
!INDEED, sometimes commands are “skipped”, I’ve noticed it as well, but each one I traced was validly skipped in fact. Since there is also a limit on how many times you can tip the same person :-) I kept forgetting that as well !WEIRD enough :-)
I did notice from time to time that almost all bots stop responding to anything at all for a period of time. And then I mean almost all, not just mine, but also !LOL and !ALIVE. Then after a while they picked up again. And !DOOK seems to be least prone to this issue. I think it is a node issue, but all my bots are using different nodes, so it must be some kind of “synced node issue”. Possible, as I do see node errors passing by regularly in the bot’s logs as well…
)