Re: [Licq-main] 1.1.0 release coming soon?
On Thu, Feb 14, 2002 at 09:07:35PM +0530, Kingsly John wrote: > Well.. for most people it only happens the first time... after which you > know that you can't do that... so you won't use it until you grab the next > snapshot! ;-) I'd rather know in advance what I can't do, so it doesn't crash. :-) > |I gather that the UDP protocol has been completely stripped out of > |the newer version. It would be useful to have one that supports > |both, selectable by the user. > As long as you are using the UDP version to talk to the server it's going > to gobble up all your messages. I know this (but I *am* using the UDP version and I can live with it). > They are *AOL* they can do just about anything they please and get away > with it... but they still love to cry foul when a someone else does the > same thing! ;-) Incidentally, for curiosity's sake I just downloaded the latest and greatest (ha!) Java ICQ from their web page and tried it out using the java1.1 JRE installed on Solaris 8. The "Enter your ICQ# and Password" box is still there about 45 minutes after I pressed "OK", with the little icon still spinning. Great software, eh? ;-) imc PS: unrelated stupid question: I have no real idea what UDP actually is, but I'm given the impression that it just consists in sending packets with no established connection [I guess I'm wrong about that because netstat shows it as an established connection]. So if I'm configuring a firewall then do I need to allow some incoming UDP ports as well as the outgoing one? Or does opening the outgoing port automatically allow the incoming ones to get back? ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Thu, 14 Feb 2002, Ian Collier wrote: |I haven't tried the CVS version, mostly out of laziness but also |because I'd rather have something that's stable than something |that's half-finished. I've heard reports that it crashes if you |try to do something that's not implemented. Well.. for most people it only happens the first time... after which you know that you can't do that... so you won't use it until you grab the next snapshot! ;-) | If that version is to be released then that behaviour has to be fixed |(try putting up a "not implemented!" message instead). You can submit a patch to that effect... but I'm sure the developers would rather see a working implementation than a choiceless popup! But the CVS version is pretty much usable... and it doesn't crash all that often either... I don't use the stuff that crashes it.. and it's not like it crashes on some random incoming event or anything. |I gather that the UDP protocol has been completely stripped out of |the newer version. It would be useful to have one that supports |both, selectable by the user. As long as you are using the UDP version to talk to the server it's going to gobble up all your messages. |Personally I don't understand how AOL can break their servers so badly |that they pretend to support the old protocol and pretend to send your |messages while throwing them away. They are *AOL* they can do just about anything they please and get away with it... but they still love to cry foul when a someone else does the same thing! ;-) Kingsly ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Wed, Feb 13, 2002 at 05:23:13PM -0600, Jamin W. Collins wrote: > 2) the current actual release of Licq is broken (ICQ no longer supports > use of that protocol version) So then which version do they provide to Linux users as a download from their site?... [answer: ICQJava 0.981a] Actually, I'm still on 1.0.0 and as long as I don't receive a message from a new (high-numbered) user or try to send via server it works mostly fine. I haven't tried the CVS version, mostly out of laziness but also because I'd rather have something that's stable than something that's half-finished. I've heard reports that it crashes if you try to do something that's not implemented. If that version is to be released then that behaviour has to be fixed (try putting up a "not implemented!" message instead). I gather that the UDP protocol has been completely stripped out of the newer version. It would be useful to have one that supports both, selectable by the user. Personally I don't understand how AOL can break their servers so badly that they pretend to support the old protocol and pretend to send your messages while throwing them away. imc ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Thu, 14 Feb 2002, Simon Oosthoek wrote: |On Thu, Feb 14, 2002 at 01:08:27AM +0100, Tim van Erven wrote: |> > 2) the current actual release of Licq is broken (ICQ no longer supports |> > use of that protocol version) |> |> Well, I only switched to the CVS version very recently and 1.0.4 used |> to mostly work for me. But if it's gotten to the point where it's |> really unusable perhaps an interim release is in order. | |Although I do know how to access cvs (obviously ;-) I usually work with |ready, stable binary packages (rpm/deb). I'm told that someone is providing rpms of the daily snapshots... so people not interested in dirtying their hands with compiling from sources can always use that. BTW something I've noticed happen to people who use "checkinstall" ... when they install the "qt-gui" it wipes out their qt install! ;-) .. ofcourse this is not a licq bug ... but it's funny when someone tells you I just compiled and installed licq-CVS and KDE stopped working! :o) Kingsly ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Thu, Feb 14, 2002 at 01:08:27AM +0100, Tim van Erven wrote: > > 2) the current actual release of Licq is broken (ICQ no longer supports > > use of that protocol version) > > Well, I only switched to the CVS version very recently and 1.0.4 used > to mostly work for me. But if it's gotten to the point where it's > really unusable perhaps an interim release is in order. Although I do know how to access cvs (obviously ;-) I usually work with ready, stable binary packages (rpm/deb). The only reason I started on licq-cvs was that 1.0.4 was absolutely unreliable and I was unable to communicate through it effectively (you never know if some message was actually received until you get a confirmation, and knowing the style of icq communication, it relies on a reliable history of messages) I think it would be good to release a binary package with the title: alpha or even beta (I never crash it). This should of course be accompanied by a good explanation of why and what's not working yet. I think this will help licq users a lot, it might even drive more distro-programmers to help fix the bugs, since they want to include a working icq-clone in their distro releases. Cheers Simon ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Wed, Feb 13, 2002 at 05:23:13PM -0600, "Jamin W. Collins" <[EMAIL PROTECTED]> wrote: > On Wed, 2002-02-13 at 17:06, Tim van Erven wrote: >>> I think these could be pushed off for a while, maybe added an update >>> release to follow. GnomeICU doesn't have support for these yet, either. >>> The big thing would be to get a functional release out that provides >>> support for most the new protocol. This would be highly benificial for >>> those that don't normally run the CVS version. >> >> Why? I think releasing licq in its current state would only confuse >> people not on this list. At least if they get it from CVS they'll know >> they're running a devel version. If they're running an official release >> they'll start to expect things like all features working and all that. > > Mainly for two reasons: > > 1) contrary to popular believe not all linux users know how to use CVS > and compile applications Which acts as a nice selection mechanism: those who can't figure out how to use CVS (and that's ok, we're all still learning!) generally don't follow licq-devel very closely and therefore wouldn't be up to speed on all the program's quircks. > 2) the current actual release of Licq is broken (ICQ no longer supports > use of that protocol version) Well, I only switched to the CVS version very recently and 1.0.4 used to mostly work for me. But if it's gotten to the point where it's really unusable perhaps an interim release is in order. -- Tim van Erven <[EMAIL PROTECTED]> ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
Jamin W. Collins wrote: > On Wed, 2002-02-13 at 17:06, Tim van Erven wrote: > > > Mainly for two reasons: > > 1) contrary to popular believe not all linux users know how to use CVS > and compile applications Thats what the snapshots are for ;-) > 2) the current actual release of Licq is broken (ICQ no longer supports > use of that protocol version) > Well... As they get to the news section, they read something like Only CVS works couse bladiblah... *most* users will be that smart to find out they should get the sanpshot. NB: I AGREE, licq should shortly releasy a /funktional/ newrelease, but user must be able to wrk with it. It now crashes couse of unimplemented features, that shouldn't be in such a release. --POSSEBILITY! Release 1.1.0-APLA-0 or so, that should be enough to understand, eeeh... this one can crash! If ya get my point. Arjen Heidinga ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Wed, 2002-02-13 at 17:06, Tim van Erven wrote: > > I think these could be pushed off for a while, maybe added an update > > release to follow. GnomeICU doesn't have support for these yet, either. > > The big thing would be to get a functional release out that provides > > support for most the new protocol. This would be highly benificial for > > those that don't normally run the CVS version. > > Why? I think releasing licq in its current state would only confuse > people not on this list. At least if they get it from CVS they'll know > they're running a devel version. If they're running an official release > they'll start to expect things like all features working and all that. Mainly for two reasons: 1) contrary to popular believe not all linux users know how to use CVS and compile applications 2) the current actual release of Licq is broken (ICQ no longer supports use of that protocol version) Jamin W. Collins ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Wed, Feb 13, 2002 at 01:59:52PM -0600, "Jamin W. Collins" <[EMAIL PROTECTED]> wrote: > On Wed, 13 Feb 2002 20:42:23 +0100 > "" <[EMAIL PROTECTED]> wrote: >>> just out of curiosity, the CVS tree seems to be stable the last few >>> weeks, is licq 1.1.0 about to be released as stable version? > (snip) >>> PS, I say go for it, I'm running the cvs version and I don't have >>> any problems, I can send through server, authorize, search, etc. no >>> crashes either. >>> >> Yap, but update your info isn't not implemented, send file either not. >> And not to forget SMS support.. :) > > I think these could be pushed off for a while, maybe added an update > release to follow. GnomeICU doesn't have support for these yet, either. > The big thing would be to get a functional release out that provides > support for most the new protocol. This would be highly benificial for > those that don't normally run the CVS version. Why? I think releasing licq in its current state would only confuse people not on this list. At least if they get it from CVS they'll know they're running a devel version. If they're running an official release they'll start to expect things like all features working and all that. -- Tim van Erven <[EMAIL PROTECTED]> ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
On Wed, 13 Feb 2002 20:42:23 +0100 "" <[EMAIL PROTECTED]> wrote: > > just out of curiosity, the CVS tree seems to be stable the last few > > weeks, is licq 1.1.0 about to be released as stable version? (snip) > > PS, I say go for it, I'm running the cvs version and I don't have > > any problems, I can send through server, authorize, search, etc. no > > crashes either. > > > Yap, but update your info isn't not implemented, send file either not. > And not to forget SMS support.. :) I think these could be pushed off for a while, maybe added an update release to follow. GnomeICU doesn't have support for these yet, either. The big thing would be to get a functional release out that provides support for most the new protocol. This would be highly benificial for those that don't normally run the CVS version. Jamin W. Collins ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] 1.1.0 release coming soon?
Simon Oosthoek wrote: > Hi all > > just out of curiosity, the CVS tree seems to be stable the last few weeks, > is licq 1.1.0 about to be released as stable version? > > Cheers > > Simon > > PS, I say go for it, I'm running the cvs version and I don't have any > problems, I can send through server, authorize, search, etc. no crashes > either. > Yap, but update your info isn't not implemented, send file either not. And not to forget SMS support.. :) greetz Arjen Heidinga ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
[Licq-main] 1.1.0 release coming soon?
Hi all just out of curiosity, the CVS tree seems to be stable the last few weeks, is licq 1.1.0 about to be released as stable version? Cheers Simon PS, I say go for it, I'm running the cvs version and I don't have any problems, I can send through server, authorize, search, etc. no crashes either. ___ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
