[Bug 43166] Sending chatstate messages in muc doesn't please some server

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Feb 22 09:43:22 CET 2013


https://bugs.freedesktop.org/show_bug.cgi?id=43166

--- Comment #13 from Will Thompson <will.thompson at collabora.co.uk> ---
(In reply to comment #12)
> No, original bug reporter, my branches here don't fix your case yet, but
> they are working towards it!

And now, the top three patches of
http://cgit.collabora.com/git/user/wjt/telepathy-gabble/log/?h=43166-muc-rate-limit
do a little more clean-up and then fix the original bug as best we can: if we
ever get a <message type='error'><error type='wait'> from a MUC, we disable
sending typing notifications for that MUC. This still means that the first time
you send a message very quickly, the message will be rejected and you'll have
to re-send it, but it's at least recoverable.

https://bugzilla.gnome.org/show_bug.cgi?id=694251 is an untested Empathy branch
which, together with this Gabble branch, should make the chat window show the
error message from the server (in this case, "Traffic rate limit is exceeded")
rather than a string corresponding to one of
http://telepathy.freedesktop.org/spec/Channel_Type_Text.html#Enum:Channel_Text_Send_Error
(in this case, Too_Long, because that's the best code we have for this
situation, and the server genuinely rejecting the message because it's too long
looks the same to us as the server rate-limiting some other way).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.



More information about the telepathy-bugs mailing list