Re: [Licq-devel] Future of Licq

2006-03-31 Thread Arne Schmitz
Am Freitag, 31. März 2006 07:19 schrieb Jon Keating: > Hmm. I guess the reason that this hasn't been fixed is that it works for > me, and no one really complained about it being a big problem. If you have > GPGME setup and working correctly, it works pretty easily. Works for me, too. No problems s

[Licq-devel] Re: [Licq-cvs] r4384 - in trunk/licq: include src

2006-03-31 Thread Arne Schmitz
Am Donnerstag, 30. März 2006 16:01 schrieb [EMAIL PROTECTED]: > Log: > Fix uploading our info to the server, it's not perfect but works... for the > most part. Unfortunately, even ICQ5 doesnt work perfectly for some reason. > > Add some more debugging output to the encoding error messages. I now g

Re: [Licq-devel] Future of Licq

2006-03-31 Thread QnD [Joachim Staib]
Hi Jon, good to know that I'm not the only one who is "a bit stressed" with the current licq :) With the "least common denominator" I mean that every IM which can handle multiple protocols only supports what all have in common, leaving out the things that are important to decide for a specific p

Re: [Licq-devel] Future of Licq

2006-03-31 Thread Martin Garbe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Keating wrote: > On Fri, Mar 31, 2006 at 05:36:44AM +0200, QnD [Joachim Staib] wrote: > > >>- Things seem to be so unorganized. There are big steps to do, for example >>better plugin integration, video support, bug hunting and what comes >>

Re: [Licq-devel] Future of Licq

2006-03-31 Thread Jon Keating
On Fri, Mar 31, 2006 at 04:32:13PM +0200, QnD [Joachim Staib] wrote: > good to know that I'm not the only one who is "a bit stressed" with the > current licq :) Well, I have been stressing over it for awhile, but just didnt have the motivation to do to it all by myself. > With the "least common d

Re: [Licq-devel] Future of Licq

2006-03-31 Thread Jon Keating
On Fri, Mar 31, 2006 at 10:50:39PM +0200, Martin Garbe wrote: > First I thought about implementing the encryption as plugin. But later I > saw that this is not possible. So I needed to make the changes in the > base code. > The encryption code as plugin would be very good. The aim should be to > mi