如何做到“专业”？ IM 机器人可以避免被踢下线或被锁定吗？
我正在寻求开发一个可扩展的 IM 机器人（又名自动化服务代理）。 之前已经做过，我想知道使用什么方法来维护可靠性。我发现扩展存在两个直接问题：
1）在 AIM 上，如果太多用户警告您，您可能会被踢出。我的机器人不会发送垃圾邮件或执行任何恶意操作，但漏洞仍然存在。
2) 如果存在网络问题，并且机器人连续登录/注销次数过多，AOL 会将其锁定一段未知的时间。
I'm looking to develop a scalable IM bot (aka Automated Service Agent). It's been done before and I'm wondering what methods are used to maintain reliability. I see two immediate problems with scaling:
1) On AIM, you can be kicked off if too many users warn you. My bot does not spam or do anything malicious but the vulnerability is still there.
2) If there are network problems, and the bot signs on/off too many times in a row, AOL will lock it out for an unknown period of time.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
以下是一些检测预防措施：
机器人可以使用多个用户帐户，因此其活动不太可能被检测到。
机器人可以使用代理服务器，通过隐藏其真实 IP 地址来进一步隐藏检测。
可以根据网络规则对机器人进行编程，并且可以简单地防止其违反其逻辑规则。
可以
此外，针对您的第一个问题，实际报告问题的人数比您预期的要少。
此外，这纯粹是推测，根据网络规则，可以模拟两个或多个机器人（以及多个用户帐户）之间足够的合法活动，因此以抵消所做的实际报告。
针对第二个问题，对于多个帐户，机器人在发生故障时只会移动到下一个帐户。
Here are some preventative measures for detection:
A bot can use several user accounts, so that its activity is less likely to be detected.
A bot can use proxy servers to hide detection even further by obscuring its real IP address.
A bot can be programmed with the network's rules in mind, and is simply prevented from breaking those rules in its logic.
Also, in response to your first problem, fewer people than you might expect will actually report a problem.
Additionally, and this is purely speculative, depending on the network's rules, it could be possible to simulate enough legitimate activity between two or more bots (and several user accounts), so as to offset the actual reports that are made.
In response to problem number two, with multiple accounts, the bot will just move to the next account when a failure occurs.
只是一些想法。
关于#1，你正在处理人际互动。如果你的机器人不会惹恼或激怒人们，那么我怀疑大多数人会关心。聊天机器人的第一条规则（恕我直言）是与许多来自不同背景的人进行测试。记录他们的反应，以及他们对与机器人交互的感受。您还可以通过这种方式收集良好的数据来提高机器人的理解能力。
关于#2，您需要编写一个有效的速率限制器。如果短时间内出现少量断线，可能可以立即重新连接，但如果断线变得更加频繁，那么您就需要更多地退出。总的来说，这实际上对服务有好处，因为如果他们遇到服务器端问题，并且当他们试图提出问题时，会有一大群机器人扑向他们，这会很痛苦。
Just some thoughts.
Regarding #1, you're dealing with human interaction. If your bot doesn't annoy or piss people off, then I doubt that most people will care. The #1 rule with chat bots (IMHO) is to test it with a number of people from different backgrounds. Record their responses, and how they feel about interacting with the bot. You can also collect good data to improve your bots comprehension skills this way.
Regarding #2, you need to code an effective rate limiter. If there's a small number of flake outs in a short period of time its probably ok to reconnect right away, but if they become more frequent, then you'll need to back off more. This is actually good for the service in general, because if they're experiencing server side problems, and there's a horde of bots pouncing on them when they try to bring things up that's a pain.