-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages are not sent #9
Comments
Do these happen to have quotes? |
I just tried, I can confirm that message with quotes are not sent. I'll try to see if it's limited quotes. |
This is not limited to quotes. These messages were sent successfully:
Just a few seconds after, this one (and all the following) were not sent:
Maybe non-ASCII characters are also an issue. I'll try to do more tests with friends and come back with the results here. |
Results so far: double quotes are always killing the communication. Non-ASCII characters are actually perfectly fine, it seems it's related to a specific flow of messages rather than individual messages. For what we've observed, there is some kind of queuing/rate limiting be I'm not sure if it's bitlbee-facebook or Facebook. I'll add/enable some debug so I can further investigate. Some messages were delayed for as long as 3 minutes ! |
This issue will require more investigation. I would assume there is some sort of limit. |
Submitted PR #12 to deal with the double quotes issue |
This should be resolved as of 059b686. |
Within 3 hours, with about 200 lines sent from bitlbee-facebook, there are about 15-20 not sent correctly (and sometime I don't get some messages too). I don't know how nor why, there are no error/disconnection on status the console.
The text was updated successfully, but these errors were encountered: