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. 😁 🙏 💚 ✨ 🤙
You are viewing a single comment's thread from:
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