Thank you very much!!
I urgently need to go back to the coastline! Missing it!
You wonβt believe this: Iβve been tipping like an idiot the past 30minutes, only !DOOK replied!
!ALIVE
!LOL
!INDEED
You're very welcome, absolutely! I'm sure! Me too! Yes, when the other bots fall my the wayside, DOOK does a seem to keep pooping along! πππβ¨π€
Da !DOOK is something special indeed :-) It's as if the thing is alive straight on the blockchain itself, not on some node or anything :-D
I think in fact that the guy is running his own node, and doing that well, so that he always ha a reliable connection. Not sure, but it is impressive !INDEED
!INDEED it sure is a special token, and it sure seems like it! It's seems to be super reliable! Yeah, I'm sure running his own node helps a bit...lol! It's very impressive, especially for a new project!
I saw the string of BBH notifications as it caught up. Yep, !INDEED came back online quite quickly last night. It's been offline for over half an hour at the moment, however. πππβ¨π€
Yeah, !BBH was lagging because it had chocked the night before on some bad json response from a node. Made that part a bit more resilient, and restarted it.
As for !INDEED, I did see that it wasn't tipping or replying, yet, while looking at the logs, I could clearly see it being active and doing its work.
I think it was a node thing, heard some other people complaining about it as well...
Ah OK, good, I'm glad to hear that you made it more resilient to this sort of thing. Hrmmm...that is very interesting about !INDEED indeed! That must be node issue then, especially if it's working on the backend, with periodic dead zones on the frontend. Does it try to catch up when it starts working again? I see BBH doing that, but I haven't noticed it yet with INDEED, which seems to miss calls if they're made during one of these dead-zone times. π π π β¨ π€
The codebase for both is still the same at the moment, whenever I make a change to one, I make it to the other one as well if the concept allows for it. And regarding the conceptual differences between the bots, I try to keep those in the settings and configuration part of things.
The difference was between what happened, !BBH had crashed, so when it came back online, it started catching up. !INDEED didn't crash, but didn't get the blocks it needed, so it skipped them.
!LOLZ
Oh, OK, that makes sense, and it's also what I figured. That's also very good to know about how conceptual differences between the bots are handled. Ahhh, got it, now I see why there was a different experience for each of them. Thanks for the explanation! πππβ¨π€
Thank you very much!!
I urgently need to go back to the coastline! Missing it!
You wonβt believe this: Iβve been tipping like an idiot the past 30minutes, only !DOOK replied!
!ALIVE
!LOL
!INDEED
You're very welcome, absolutely! I'm sure! Me too! Yes, when the other bots fall my the wayside, DOOK does a seem to keep pooping along! πππβ¨π€
!INDEED
Da !DOOK is something special indeed :-) It's as if the thing is alive straight on the blockchain itself, not on some node or anything :-D
I think in fact that the guy is running his own node, and doing that well, so that he always ha a reliable connection. Not sure, but it is impressive !INDEED
!INDEED it sure is a special token, and it sure seems like it! It's seems to be super reliable! Yeah, I'm sure running his own node helps a bit...lol! It's very impressive, especially for a new project!
!BEER
!VSC (testing)
!BBH is running, but is still catching upβ¦
And while checking again just now, I see !INDEED back in action as well!
I saw the string of BBH notifications as it caught up. Yep, !INDEED came back online quite quickly last night. It's been offline for over half an hour at the moment, however. πππβ¨π€
Yeah, !BBH was lagging because it had chocked the night before on some bad json response from a node. Made that part a bit more resilient, and restarted it.
As for !INDEED, I did see that it wasn't tipping or replying, yet, while looking at the logs, I could clearly see it being active and doing its work.
I think it was a node thing, heard some other people complaining about it as well...
Ah OK, good, I'm glad to hear that you made it more resilient to this sort of thing. Hrmmm...that is very interesting about !INDEED indeed! That must be node issue then, especially if it's working on the backend, with periodic dead zones on the frontend. Does it try to catch up when it starts working again? I see BBH doing that, but I haven't noticed it yet with INDEED, which seems to miss calls if they're made during one of these dead-zone times. π π π β¨ π€
The codebase for both is still the same at the moment, whenever I make a change to one, I make it to the other one as well if the concept allows for it. And regarding the conceptual differences between the bots, I try to keep those in the settings and configuration part of things.
The difference was between what happened, !BBH had crashed, so when it came back online, it started catching up. !INDEED didn't crash, but didn't get the blocks it needed, so it skipped them.
!LOLZ
Oh, OK, that makes sense, and it's also what I figured. That's also very good to know about how conceptual differences between the bots are handled. Ahhh, got it, now I see why there was a different experience for each of them. Thanks for the explanation! πππβ¨π€
!INDEED
@borniet likes your content! so I just sent 1 BBH(2/5)@tydynrain! to your account on behalf of @borniet.
(html comment removed:
)