Opened at 2010-02-08T22:48:33Z
Closed at 2010-04-12T00:10:54Z
#564 closed defect (worksforme)
Bitlbee does not allow communication with bots on AIM
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | BitlBee | Version: | 1.2.4 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
This might or might not be a Bitlbee bug (best way to test is to add a few bots to an AIM account connected through Bitlbee).
Either way, almost every message sent to and from an AIM bot (possibly other services' bots too, but I don't know of any on MSN, Yahoo, or Jabber) do not get delivered.
One bot was able to message me, but that quickly died down and I am unable to message them (right after they messaged me). The bots just do not seem to recieve messages from me, and they never reply.
Buddy Send_Buffer is set to False Away Devoice is set to true
I have tried both PMing the bots (which should message them through my account, as it successfully worked once, but other attempts to message the same bot right after a reply fail) and typing their name: and my message.
Both fail sliently, with debug=true and debug=false. Bitlbee does not report any errors of any kind.
Perhaps it can be that I connect to Bitlbee's testing server from Mibbit (and over a secured link, then Mibbit connects to the server from another secured link).
Attachments (0)
Change History (4)
comment:1 Changed at 2010-02-08T22:50:25Z by
comment:2 Changed at 2010-02-11T04:53:57Z by
It would seem that this issue had to do with the Private setting.
Setting it to True started this problem (maybe the bots were trying to open new windows when they were messaging me, and it was not allowed with Private=True... I don't know)
Setting it to False stopped this problem, allowing me (100% of the time) to message the bots as long as I addressed them by name (an example would be 'AIMBot: Hello').
It did stop me from using Mibbit WebChat's PM button on a name to message them, but it did fix this problem.
comment:3 Changed at 2010-02-11T04:55:33Z by
If you will, wilmer, can you go ahead and close this issue?
Leave it here so others who might have this problem be directed here to this issue, though. :)
comment:4 Changed at 2010-04-12T00:10:54Z by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Thanks, I would have no clue myself what this could be. :-)
(I am the author)
If you wish to contact me for any reason about this report, please use: XANAVirus {A T} gmail {D O T} com