Miranda NG Official Community Forum
Forum for English speaking Miranda NG users => Support/Help => Topic started by: pseudox on 17 02 2016, 17:04:51
-
I get the following message when I log into aim via MIranda NG x86
"AOL System Msg , : Hello. The version of AIM you’re using is going away as of March 15. To continue using AIM, please download the latest version here (http://download.newaol.com/aim/win/AIM_Install.exe)."
-
I also got the same message earlier and now (for some reason) I cant connect to AIM at all.
-
Well, AIM has been kinda wonky, on and off. It still works, but I have also received this message, so I assume it will not be possible to log in starting with 15th of March - unless someone updates the plugin; assuming the network specification is out.
Make sure to notify your AIM contacts you might be taking a long time off.
-
Strange politic from AOL. There are not so many users remained which still use their system. And with that update they are going cut of many of them. I think there are not so many users who want to install different soft for that unpopular in nowdays message system
-
I agree; and I bet there is also no published protocol detail and if anything, it will need to be reverse-engineered...
-
You can use pidgin (libpurple) source code to implement updates.
I believe it can be found here:
https://pidgin.im/download/source/
Pidgin is working just fine right now with AIM.
Ticket: http://trac.miranda-ng.org/ticket/1186
-
Please check if it has been fixed.
-
It's not working.
I think pidgin does something differently, it uses "clientLogin". If you uncheck this option in pidgin, it behaves exactly the same as miranda - times out after a few seconds.
Miranda logs:
[10:49:33 4500] [Aimpix] Connection request to slogin.oscar.aol.com:5190 (Flags 4)....
[10:49:33 4500] [Aimpix] (11040578) Connecting to server slogin.oscar.aol.com:5190....
[10:49:33 4500] [Aimpix] (11040578) Connecting to ip 64.12.27.71:5190 ....
[10:49:39 4500] [Aimpix] src\netlibopenconn.cpp 727: connect() failed (1460)
My guess is that Pidgin uses a different method of connection.
-
It's not working.
I think pidgin does something differently, it uses "clientLogin". If you uncheck this option in pidgin, it behaves exactly the same as miranda - times out after a few seconds.
Miranda logs:
[10:49:33 4500] [Aimpix] Connection request to slogin.oscar.aol.com:5190 (Flags 4)....
[10:49:33 4500] [Aimpix] (11040578) Connecting to server slogin.oscar.aol.com:5190....
[10:49:33 4500] [Aimpix] (11040578) Connecting to ip 64.12.27.71:5190 ....
[10:49:39 4500] [Aimpix] src\netlibopenconn.cpp 727: connect() failed (1460)
My guess is that Pidgin uses a different method of connection.
Current miranda-ng night build only works with AIM if you specify this:
Host: login.oscar.aol.com
Port: 5190
put checkmark Disable SSL
Yes, need to look into Pidgin how they implemented their clientLogin with Encryption.
-
SSL disabled by default (until someone implement encryption)
http://trac.miranda-ng.org/changeset/16563
So plugin works without encryption?
-
SSL disabled by default (until someone implement encryption)
http://trac.miranda-ng.org/changeset/16563
So plugin works without encryption?
Yes it works without encryption for now.
You need to use night build from miranda-ng to get AIM working.
-
Ok. I'm ask this because developers are planning stable release. Half-working AIM better, than non-working :)
Also I'm add warning about broken SSL to our wiki.
-
Please test AIM SSL in next nightly build (http://trac.miranda-ng.org/changeset/16608)
-
It works! :THUMBS UP:
-
Yup, works for me too
-
Yup, works for me too
It works!
The only thing that works right now is plaintext connection over aol.
clientLogin is not working at the moment with SSL.
-
The "development version" updates work mostly fine with AIM, but I get the message "Unknown error when attempting to modify a group. Error code 0xa" whenever I log in. I have to click OK a dozen times before it stays gone.
The "stable version" does not work with AIM at all still.
-
I'm noticing several odd bugs with Miranda NG, Development Build, using the AIM protocol.
1. As previously mentioned, I get "Unknown error when attempting to modify a group. Error code 0xa" about 20 times, and have to click Ok each.
2. After a day or two, suddenly I could no longer connect to AIM. I'd pick "Online" but the icon would stay grey and offline. I had to go into "Accounts" delete the AIM account, and then re-add it, and now I can connect again. Very odd.
Using Miranda NG Version: 0.95.5 alpha build #16744
-
0.95.5 alpha build #16797
Still getting "Unknown error when attempting to modify a group. Error code 0xa"
I'm new here, is there a better place to provide this feedback? I feel like im talking into a void.
-
There are 3 places to provide feedback:
1) this forum
2) our bug tracker - http://trac.miranda-ng.org
3) chatroom on jabber - link is on homepage
It's good to put bugs on tracker. But as there is no developer dedicated to AIM, it may just lay there for a long time too... Often is best to try to talk to some dev directly in our jabber chatroom (but not everyone is going there).
Someone (I don't remember his nickname here) was implementing the "clientLogin", so maybe try to contact him.
-
The problem is known, there are other problems with ClientLogin which have to be fixed first.