This repository has been archived by the owner on Dec 28, 2021. It is now read-only.
ICQ broken since protocol update on 2018-12-28 #53
Comments
|
Hi, |
I thought that'd be the case... Too bad, because it's still my preferred client. It wouldn't have to be the original developers doing it either, I'd welcome an implementation of the new WIM protocol in licq, no matter where it comes from. ;) I don't think I can do this by myself unfortunately... small fixes like the 16-character passwords, that was easy to do, but a whole protocol implementation... uh. |
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Jul 5, 2019
licq has not been able to connect to ICQ servers since 28th December 2018, while upstream discontinued development in 2014 and has no plans to start over. Also, these packages have not been updated since 2007, so I doubt anyone has used this in a long time. licq-im/licq#53
nieder
added a commit
to fink/fink-distributions
that referenced
this issue
Oct 8, 2019
…ocol on 2019-12-28. So the licq packages can't do anything anymore. licq-im/licq#53
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since the ICQ protocol update on the 28th December 2018, licq can no longer log into the ICQ servers. This requires an updated ICQ protocol plugin!
I hope somebody is willing to fix this!
Thanks.
The text was updated successfully, but these errors were encountered: