Hi, I have a couple of questions, since there may have been a misunderstanding here.
Pidgin currently supports three auth methods for AIM: - MD5 using slogin.oscar.aol.com. Uses the DistID, does not use the DevID - clientLogin aka OpenAuth using api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has been the default setting for pidgin releases since 2009 - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in pidgin 2.11.0, released four months ago. If I'm understanding this right, the first method is being discontinued and the other two will continue working. It's possible a lot of users are using that - the account setting is a bit too visible, so users might just switch to it for the sake of changing settings. But as far as I can see, pidgin with the default configuration won't stop working. What I don't understand is why we're changing the DistID and DevID. I'm 90% sure that clientlogin sends both in the same way as the official client. Did the previous ones get invalidated? We're currently using these: Pidgin DistID: 1550 DevID: ma1cSASNCKFtrdv9 Finch: DistID: 1552 DevID: ma19sqWV9ymU6UYc Libpurple: DistID: 1553 DevID: ma15d7JTxbmVG-RP The source code says they are owned by the AIM account "markdoliner". Are these still valid? If they are, I think you can go ahead and pull the plug of the old auth method. Thanks On 14 October 2016 at 01:11, Gary Kramlich <g...@reaperworld.com> wrote: > Hi Donald, > > This is Gary Kramlich the current maintainer of Pidgin. Please excuse > my tardiness in this matter as I haven't had much time to dedicate to > Pidgin in the past few weeks. > > That said. We are staging a new version which will have this updates, > but we will most likely miss the 20161016 date. If we could get that > extended it would be great. > > Also our code base has contains two clients that connect to AIM and as > I've learned recently they do not share keys. The other clients name > is Finch and if we could get a set of keys for it that would be > awesome. Otherwise we'll just reuse the Pidgin ones for the time > being. > > Also is there a web portal or something where we can manage this keys? > If so, please respond to me directly as I assume we'll want to > control access to it. > > Thanks, > > -- > Gary Kramlich <g...@reaperworld.com> > > _______________________________________________ > Support@pidgin.im mailing list > Want to unsubscribe? Use this link: > https://pidgin.im/cgi-bin/mailman/listinfo/support _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://pidgin.im/cgi-bin/mailman/listinfo/support
