This is interesting information. One thing made me scratch my head: the WUSANG comment being the most commonly mentioned. Wasn't sure what to make of that, I run the bot and HBIT seems to get called more often, and LUV even more often. So, why WUSANG? I wondered. Then, I saw that your sample week was 5/18 to 5/24. On 5/21, dead center (of course!), the Hivebits account was attacked. Evidently WUSANG was the command of choice. I wrote about it at https://peakd.com/hivebits/@crrdlx/hbit-resource-credits (initially thinking it was just a resource credits situation).
You are viewing a single comment's thread from:
Very important for the data to line up with our temporal observations! I hadn't heard about your project prior to this, and my discovery of the WUSANG command is what led me to follow your account, which may be what lead you to come to this post, I'm not sure!
I plan to exclude such calls to bots in future analysis of comment quality, because, well, they have their place for the communities that enjoy using them and speculating on the Hive Engine tokens and various side chains that they're integrated with.
I won't lie, my query on those token call commands is sort of linked with @aggroed recently posting about changing the ability for bulk transactions to occur on the sidechains.
As with all things, it is all interconnected. I just want to learn more about the over arching comment quality on HIVE :)
I've seen the same a while ago, when I fixed the BBHbot. A bot account was simply spreading the !BBH tipping call in comments all over the place, without even owning BBH (and thus not having tipping powers). No idea what the use of it was, but it sucked bigtime. It was at that time that I started reworking the comments of the tipping bots I operate, and slowly went towards the daily summary system (or weekly now for large part of my other bots !INDEED), and have added a pretty strong blacklisting system to my bots.
I have the impression that it is not even always about gaining things, but just the "fun" of trying to break things...
Agree, it's the thrill
They'd better grow some real skills and write something useful! There's thrill in that too...
Well said. Almost everything I've ever made code or computer-wise is for one of two reasons: to make something for me to use personally or just of challenge of seeing if I can make it and get it to work.
Exactly that! Totally share those intentions, to learn or to use! And once it is built, to share.