ein Blog

woes3.

A continuation of this and that.

I've now also tried out gajim as the sending client. In contrast to psi and pidgin, this one works nicely in that it informs users of problems with delivery and also of the final error message from the server. So well done gajim!

woes2.

This is a followup to my previous post here.

Things that happened since writing the post:

• Pidgin have now acknowledged their "not showing error stanzas" bug and basically replied with it's complicated. The main problem seems to be that, like BitlBee as well, Pidgin doesn't keep a list of stanzas that were already sent, so the information that a certain message ID had an error doesn't really carry meaningful information. We can hope.
• Chatsecure have expressed dismay about the timing of my post since they think they have fixed most of the issues I complained about in an update that was released right after I published my post. I'll certainly give the new version a trial run and share my thoughts on it in a few days.
• Also there were some reactions and discussions on twitter. (including reference to yet another ejabberd annoyance)

So that's that for now. More as the story develops.

Update: I've now also looked at gajim as the sending client