Also, it can enforce SSL connections (see 1093) - that means, if SSL connection will be unsuccessful, it won't fall back to plain-text mode.
I have reduced differences with upstream version of libgadu to minimum, so following updates will be easier.
The way I would (and might) implement this would be to add a field to the Purple Plugin Info?
struct called update URL which would simply point to a text file with the latest version number of the plugin, which would be compared against the local plugin's version number.
Here's what I'll do: I come in the office long before most others.If I sign out and sign back in, it will properly display the statuses at the time of sign in. The libpurple-based client doesn't see status changes of others. Yes, this happens to all users using libpurple-based applications. Another interesting piece of information: It seems that libpurple users are displaying properly.As in, I can see people sign in and out who use libpurple clients, however I can't see status updates for people using Spark.Also, I managed to fix all warnings when building and some bugs that was present in our fork of libgadu.This version was tested under Linux 32bit and Windows 7 32bit (cywgin).