Shieldy deleting commands for other bots. #2

New issue

Closed

opened 2019-08-11 04:18:01 +00:00 by 7h3v01c3 · 2 comments

7h3v01c3 commented

2019-08-11 04:18:01 +00:00

(Migrated from github.com)

It seems with /lock-on Shieldy is also deleting commands used by some other bots.

In this case a bot with features and commands un-related to any Shieldy command. A user can call a command and the listener works for the bot and the other bot responds to the command but Shieldy deletes the command in the channel.

Or if /lock is supposed to encompass any command called in the channel I guess I missed that.

Oh, and btw you deserve this _ THANK YOU FOR THIS BOT!

It seems with /lock-on Shieldy is also deleting commands used by some other bots. In this case a bot with features and commands un-related to any Shieldy command. A user can call a command and the listener works for the bot and the other bot responds to the command but Shieldy deletes the command in the channel. Or if /lock is supposed to encompass any command called in the channel I guess I missed that. Oh, and btw you deserve this _ THANK YOU FOR THIS BOT!

backmeupplz commented

2019-08-11 22:24:28 +00:00

(Migrated from github.com)

Thank you for the kind words :) I'll try to figure out what's happening with lock. Does Shieldy delete the commands sent to other bots like /help@other_bot? Or just the unaddressed commands like /help?

Thank you for the kind words :) I'll try to figure out what's happening with lock. Does Shieldy delete the commands sent to other bots like `/help@other_bot`? Or just the unaddressed commands like `/help`?

7h3v01c3 commented

2019-08-12 05:15:57 +00:00

(Migrated from github.com)

You know it stopped doing it!

Maybe she just got overwhelmed ???

I just had the same user test it and sure enough, Shieldy ignored every request and they all went through.

I went back through the logs and it seemed to be people who joined the channel and passed captcha within an hour or two.

So I'm thinking - Shieldy just got real busy yesterday... working overtime...

Just for kicks, it was non /help or /help@other_bot requests...

In this case, it was a blockchain lookup tool /masternode and /staking so it shouldn't have been a listener issue.

I'm closing it -- so as not to waste your time anymore.

I do really appreciate your work on Shieldy!

You know it stopped doing it! Maybe she just got overwhelmed ??? I just had the same user test it and sure enough, Shieldy ignored every request and they all went through. I went back through the logs and it seemed to be people who joined the channel and passed captcha within an hour or two. So I'm thinking - Shieldy just got real busy yesterday... working overtime... Just for kicks, it was non /help or /help@other_bot requests... In this case, it was a blockchain lookup tool /masternode and /staking so it shouldn't have been a listener issue. I'm closing it -- so as not to waste your time anymore. I do really appreciate your work on Shieldy!

👍 1