Most likely it is because the summaries are not being posted through the inleo ui. Also, if you look at its profile on hive.blog, you'll see that the actual number is closer to 181k threads. For some reason they stopped getting counted around the 61k mark on inleo. I hadn't made any changes at that point.
61,0000 threads 😱
the true number is actually closer to 181 000. For some reason they stopped getting counted around 60k
Most likely it is because the summaries are not being posted through the inleo ui. Also, if you look at its profile on hive.blog, you'll see that the actual number is closer to 181k threads. For some reason they stopped getting counted around the 61k mark on inleo. I hadn't made any changes at that point.
another bot related question: are there any code prerequisites for a bot comment to show up on the inleo ui?
I'm unsure. It appears it is not possible. I simply modeled the thread transaction metadata after a regular thread
Hi, @mightpossibly,
This post has been voted on by @darkcloaks because you are an active member of the Darkcloaks gaming community.
Get started with Darkcloaks today, and follow us on Inleo for the latest updates.
Ah ok, then you got leothreads in the json metadata somewhere I guess ...
interesting, so you programmed the bot to use a different frontend or does it post to hive.blog as default?!
comments are constructed in the script and posted directly to chain. No front-end is used
its the number of threads it has made to others replies. It didn't make it's own thread
yeah that makes sense actually.
if it made it's own thread it would be shown on it's feed
i know! that’s why i switched from PARENT to ALL as you can see at the red mark on the screenshot 😉
there is an AI bot here? Impressive
its likely because it just responds to people's call and not make an actual thread on its own.
The bot is a hard worker