Re: AIM login

[Mark Zeldis]

ird said in the original email "No usage since August 2014 so no 
>>>>>>>> need new DistID and DevID", which is clearly wrong. There's also that 
>>>>>>>> "another libpurple" with distid 1502 which doesn't match any client we 
>>>>>>>> own, and we don't know how you found that one.
>>>>>>>> 
>>>>>>>> So for the sake of avoiding a roundtrip in our communication and 
>>>>>>>> getting the release packaged ASAP, we went ahead and used the 
>>>>>>>> remaining 1718 distid for finch.
>>>>>>>> 
>>>>>>>> This looks like it was a mistake, since we're now getting "Method not 
>>>>>>>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>>>>>>> 
>>>>>>>> Did the 1718 distid get invalidated? Can you re-enable it so that we 
>>>>>>>> don't have to make another release?
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>>> 
>>>>>>>>> On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:
>>>>>>>>> All, 
>>>>>>>>> 
>>>>>>>>> My comments are inline.
>>>>>>>>> 
>>>>>>>>> Thanks,
>>>>>>>>> 
>>>>>>>>> Donald Le
>>>>>>>>> Tech Director | Product Management and Support AIM Platform
>>>>>>>>> O: 703-265-5645 | M: 703-678-1073
>>>>>>>>> AIM: donald...@teamaol.com
>>>>>>>>> AOL Inc. 22070 Broderick Drive Dulles, VA 20166
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com> 
>>>>>>>>>> wrote:
>>>>>>>>>> All,
>>>>>>>>>> 
>>>>>>>>>> Quick update: we had to delay AIM client upgrade due to other 
>>>>>>>>>> integration, the date is tbd.
>>>>>>>>>> I will answer your questions in the coming weeks.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Thanks,
>>>>>>>>>> 
>>>>>>>>>> Donald Le
>>>>>>>>>> Tech Director | Product Management and Support AIM Platform
>>>>>>>>>> O: 703-265-5645 | M: 703-678-1073
>>>>>>>>>> AIM: donald...@teamaol.com
>>>>>>>>>> AOL Inc. 22070 Broderick Drive Dulles, VA 20166
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>>>>>>>>>> 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
>>>>>>>>> 
>>>>>>>>>  All DistID used for login.oscar.aol.com and 
>>>>>>>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM client 
>>>>>>>>> upgrade will start Feb 24th 2017.
>>>>>>>>>>> 
>>>>>>>>>>> - clientLogin aka OpenAuth using
>>>>>>>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>>>>>>>>>>> been the default setting for pidgin releases since 2009
>>>>>>>>> 
>>>>>>>>>  This login path will stay but you need to update the DistID 
>>>>>>>>> and DevID. We will give you a new set. 
>>>>>>>>>>> 
>>>>>>>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced 
>>>>>>>>>>> in
>>>>>>>>>>> pidgin 2.11.0, released four months ago.
>>>>>>>>> 
>>>>>>>>>  Same as above with OpenAuth. 
>>>>>>>>>>> 
>>>>>>>>>>> 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.
>>>>>>>>> 
>>>>>>>>>  If Pidgin uses DistID = 1502 or 0, the login will be 
>>>>>>>>> blocked. 
>>>>>>>>>>> 
>>>>>>>>>>> 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?
>>>>>>>>> 
>>>>>>>>>  Yes. 
>>>>>>>>>>> 
>>>>>>>>>>> We're currently using these:
>>>>>>>>>>> 
>>>>>>>>>>> Pidgin
>>>>>>>>>>> DistID: 1550
>>>>>>>>>>> DevID: ma1cSASNCKFtrdv9
>>>>>>>>> 
>>>>>>>>>  I reached out to Pidgin, see below.
>>>>>>>>>  
>>>>>>>>> From: Donald Le <donald...@teamaol.com>
>>>>>>>>> Date: Thu, Sep 22, 2016 at 6:20 PM
>>>>>>>>> Subject: Re: AIM login
>>>>>>>>> To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin 
>>>>>>>>> Support List <support@pidgin.im>
>>>>>>>>> 
>>>>>>>>> new DevID = do1UCeb5gNqxB1S1
>>>>>>>>> new distID = 1715
>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Finch:
>>>>>>>>>>> DistID: 1552
>>>>>>>>>>> DevID: ma19sqWV9ymU6UYc
>>>>>>>>> 
>>>>>>>>>  No usage since August 2014 so no need new DistID and DevID.
>>>>>>>>>>> 
>>>>>>>>>>> Libpurple:
>>>>>>>>>>> DistID: 1553
>>>>>>>>>>> DevID: ma15d7JTxbmVG-RP
>>>>>>>>> 
>>>>>>>>>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>>>>>>>>> 
>>>>>>>>> I found another Libpurple 
>>>>>>>>> DistID: 1502 with no DevID >> new DistID = 1718, new DevID = 
>>>>>>>>> ma18nmEklXMR7Cj_
>>>>>>>>>>> 
>>>>>>>>>>> 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
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> ___
>>>>> Devel mailing list
>>>>> de...@pidgin.im
>>>>> https://pidgin.im/cgi-bin/mailman/listinfo/devel
>>>> 
>>> 
>> 
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Crystal Birnie]

gt;>>>>>>
>>>>>>>
>>>>>>> *Donald Le*
>>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>>> <%28703%29%20678-1073>
>>>>>>> *AIM*: donald...@teamaol.com
>>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>> 
>>>>>>>
>>>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All,
>>>>>>>>
>>>>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>>>>> integration, the date is tbd.
>>>>>>>> I will answer your questions in the coming weeks.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>> *Donald Le*
>>>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>>>> <%28703%29%20678-1073>
>>>>>>>> *AIM*: donald...@teamaol.com
>>>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>>> 
>>>>>>>>
>>>>>>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>  All DistID used for login.oscar.aol.com and
>>>>>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM
>>>>>>> client upgrade will start Feb 24th 2017.
>>>>>>>
>>>>>>>>
>>>>>>>>> - clientLogin aka OpenAuth using
>>>>>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID.
>>>>>>>>> Has
>>>>>>>>> been the default setting for pidgin releases since 2009
>>>>>>>>>
>>>>>>>>
>>>>>>>  This login path will stay but you need to update the DistID
>>>>>>> and DevID. We will give you a new set.
>>>>>>>
>>>>>>>>
>>>>>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID.
>>>>>>>>> Introduced in
>>>>>>>>> pidgin 2.11.0, released four months ago.
>>>>>>>>>
>>>>>>>>
>>>>>>>  Same as above with OpenAuth.
>>>>>>>
>>>>>>>>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>
>>>>>>>  If Pidgin uses DistID = 1502 or 0, the login will be
>>>>>>> blocked.
>>>>>>>
>>>>>>>>
>>>>>>>>> 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?
>>>>>>>>>
>>>>>>>>
>>>>>>>  Yes.
>>>>>>>
>>>>>>>>
>>>>>>>>> We're currently using these:
>>>>>>>>>
>>>>>>>>> Pidgin
>>>>>>>>> DistID: 1550
>>>>>>>>> DevID: ma1cSASNCKFtrdv9
>>>>>>>>>
>>>>>>>>
>>>>>>>  I reached out to Pidgin, see below.
>>>>>>>
>>>>>>> From: Donald Le <donald...@teamaol.com>
>>>>>>> Date: Thu, Sep 22, 2016 at 6:20 PM
>>>>>>> Subject: Re: AIM login
>>>>>>> To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin
>>>>>>> Support List <support@pidgin.im>
>>>>>>>
>>>>>>> new DevID = do1UCeb5gNqxB1S1
>>>>>>> new distID = 1715
>>>>>>>
>>>>>>>
>>>>>>>>> Finch:
>>>>>>>>> DistID: 1552
>>>>>>>>> DevID: ma19sqWV9ymU6UYc
>>>>>>>>>
>>>>>>>>
>>>>>>>  No usage since August 2014 so no need new DistID and DevID.
>>>>>>>
>>>>>>>>
>>>>>>>>> Libpurple:
>>>>>>>>> DistID: 1553
>>>>>>>>> DevID: ma15d7JTxbmVG-RP
>>>>>>>>>
>>>>>>>>
>>>>>>>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>>>>>>>
>>>>>>> I found another Libpurple
>>>>>>> DistID: 1502 with no DevID >> new DistID = 1718, new DevID =
>>>>>>> ma18nmEklXMR7Cj_
>>>>>>>
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> ___
>>> Devel mailing list
>>> de...@pidgin.im
>>> https://pidgin.im/cgi-bin/mailman/listinfo/devel
>>>
>>
>>
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Mark Zeldis]

ent and Support AIM Platform*
>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>>> <%28703%29%20678-1073>
>>>>>>> *AIM*: donald...@teamaol.com
>>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>>
>>>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All,
>>>>>>>>
>>>>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>>>>> integration, the date is tbd.
>>>>>>>> I will answer your questions in the coming weeks.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>> *Donald Le*
>>>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>>>> <%28703%29%20678-1073>
>>>>>>>> *AIM*: donald...@teamaol.com
>>>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>>>
>>>>>>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>  All DistID used for login.oscar.aol.com and
>>>>>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM
>>>>>>> client upgrade will start Feb 24th 2017.
>>>>>>>
>>>>>>>>
>>>>>>>>> - clientLogin aka OpenAuth using
>>>>>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID.
>>>>>>>>> Has
>>>>>>>>> been the default setting for pidgin releases since 2009
>>>>>>>>>
>>>>>>>>
>>>>>>>  This login path will stay but you need to update the DistID
>>>>>>> and DevID. We will give you a new set.
>>>>>>>
>>>>>>>>
>>>>>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID.
>>>>>>>>> Introduced in
>>>>>>>>> pidgin 2.11.0, released four months ago.
>>>>>>>>>
>>>>>>>>
>>>>>>>  Same as above with OpenAuth.
>>>>>>>
>>>>>>>>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>
>>>>>>>  If Pidgin uses DistID = 1502 or 0, the login will be
>>>>>>> blocked.
>>>>>>>
>>>>>>>>
>>>>>>>>> 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?
>>>>>>>>>
>>>>>>>>
>>>>>>>  Yes.
>>>>>>>
>>>>>>>>
>>>>>>>>> We're currently using these:
>>>>>>>>>
>>>>>>>>> Pidgin
>>>>>>>>> DistID: 1550
>>>>>>>>> DevID: ma1cSASNCKFtrdv9
>>>>>>>>>
>>>>>>>>
>>>>>>>  I reached out to Pidgin, see below.
>>>>>>>
>>>>>>> From: Donald Le <donald...@teamaol.com>
>>>>>>> Date: Thu, Sep 22, 2016 at 6:20 PM
>>>>>>> Subject: Re: AIM login
>>>>>>> To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin
>>>>>>> Support List <support@pidgin.im>
>>>>>>>
>>>>>>> new DevID = do1UCeb5gNqxB1S1
>>>>>>> new distID = 1715
>>>>>>>
>>>>>>>
>>>>>>>>> Finch:
>>>>>>>>> DistID: 1552
>>>>>>>>> DevID: ma19sqWV9ymU6UYc
>>>>>>>>>
>>>>>>>>
>>>>>>>  No usage since August 2014 so no need new DistID and DevID.
>>>>>>>
>>>>>>>>
>>>>>>>>> Libpurple:
>>>>>>>>> DistID: 1553
>>>>>>>>> DevID: ma15d7JTxbmVG-RP
>>>>>>>>>
>>>>>>>>
>>>>>>>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>>>>>>>
>>>>>>> I found another Libpurple
>>>>>>> DistID: 1502 with no DevID >> new DistID = 1718, new DevID =
>>>>>>> ma18nmEklXMR7Cj_
>>>>>>>
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> ___
>>> Devel mailing list
>>> de...@pidgin.im
>>> https://pidgin.im/cgi-bin/mailman/listinfo/devel
>>>
>>
>>
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Donald Le]

;> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>>>
>>> On Mon, Mar 13, 2017 at 7:33 AM, Donald Le <donald...@teamaol.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>> *The third said in the original email "No usage since August 2014 so no
>>>> need new DistID and DevID", which is clearly wrong. There's also that
>>>> "another libpurple" with distid 1502 which doesn't match any client we own,
>>>> and we don't know how you found that one.*
>>>> I can't explain but you did the right thing to use 1718 for Finch.
>>>>
>>>>
>>>> *Did the 1718 distid get invalidated? Can you re-enable it so that we
>>>> don't have to make another release?*
>>>> Please try again now and let me know, I correct a typo in the devID
>>>> just now.
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> *Donald Le*
>>>> *Product Management and Support AIM Platform*
>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>> <%28703%29%20678-1073>
>>>> *AIM*: donald...@teamaol.com
>>>> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>>>>
>>>> On Sun, Mar 12, 2017 at 1:25 PM, dequis <d...@dxzone.com.ar> wrote:
>>>>
>>>>> Hey Donald!
>>>>>
>>>>> As you may have heard we already released pidgin 2.12.0 (together with
>>>>> libpurple and finch 2.12.0), updating the distid/devids.
>>>>>
>>>>> Here's what we used:
>>>>>
>>>>> Pidgin:
>>>>> Distid: 1715
>>>>> Devid: do1UCeb5gNqxB1S1
>>>>>
>>>>> Libpurple:
>>>>> Distid: 1717
>>>>> Devid: ma19CwYN9i9Mw5nY
>>>>>
>>>>> Finch:
>>>>> Distid: 1718
>>>>> Devid: ma18nmEklXMR7Cj_
>>>>>
>>>>> The first two are normal.
>>>>>
>>>>> The third said in the original email "No usage since August 2014 so no
>>>>> need new DistID and DevID", which is clearly wrong. There's also that
>>>>> "another libpurple" with distid 1502 which doesn't match any client we 
>>>>> own,
>>>>> and we don't know how you found that one.
>>>>>
>>>>> So for the sake of avoiding a roundtrip in our communication and
>>>>> getting the release packaged ASAP, we went ahead and used the remaining
>>>>> 1718 distid for finch.
>>>>>
>>>>> This looks like it was a mistake, since we're now getting "Method not
>>>>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>>>>
>>>>> Did the 1718 distid get invalidated? Can you re-enable it so that we
>>>>> don't have to make another release?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> My comments are inline.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>> *Donald Le*
>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>> <%28703%29%20678-1073>
>>>>>> *AIM*: donald...@teamaol.com
>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>
>>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>>>> wrote:
>>>>>>
>>>>>>> All,
>>>>>>>
>>>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>>>> integration, the date is tbd.
>>>>>>> I will answer your questions in the coming weeks.
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>> *Donald Le*
>>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>>> <%28703%29%20678-1073>
>>>>&g

Re: AIM login

[Eion Robb]

; <%28703%29%20678-1073>
>>> *AIM*: donald...@teamaol.com
>>> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>>>
>>> On Sun, Mar 12, 2017 at 1:25 PM, dequis <d...@dxzone.com.ar> wrote:
>>>
>>>> Hey Donald!
>>>>
>>>> As you may have heard we already released pidgin 2.12.0 (together with
>>>> libpurple and finch 2.12.0), updating the distid/devids.
>>>>
>>>> Here's what we used:
>>>>
>>>> Pidgin:
>>>> Distid: 1715
>>>> Devid: do1UCeb5gNqxB1S1
>>>>
>>>> Libpurple:
>>>> Distid: 1717
>>>> Devid: ma19CwYN9i9Mw5nY
>>>>
>>>> Finch:
>>>> Distid: 1718
>>>> Devid: ma18nmEklXMR7Cj_
>>>>
>>>> The first two are normal.
>>>>
>>>> The third said in the original email "No usage since August 2014 so no
>>>> need new DistID and DevID", which is clearly wrong. There's also that
>>>> "another libpurple" with distid 1502 which doesn't match any client we own,
>>>> and we don't know how you found that one.
>>>>
>>>> So for the sake of avoiding a roundtrip in our communication and
>>>> getting the release packaged ASAP, we went ahead and used the remaining
>>>> 1718 distid for finch.
>>>>
>>>> This looks like it was a mistake, since we're now getting "Method not
>>>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>>>
>>>> Did the 1718 distid get invalidated? Can you re-enable it so that we
>>>> don't have to make another release?
>>>>
>>>> Thanks
>>>>
>>>> On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> My comments are inline.
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>> *Donald Le*
>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>> <%28703%29%20678-1073>
>>>>> *AIM*: donald...@teamaol.com
>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>
>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>>> wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>>> integration, the date is tbd.
>>>>>> I will answer your questions in the coming weeks.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>> *Donald Le*
>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>>> <%28703%29%20678-1073>
>>>>>> *AIM*: donald...@teamaol.com
>>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>>
>>>>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>
>>>>>  All DistID used for login.oscar.aol.com and
>>>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM client
>>>>> upgrade will start Feb 24th 2017.
>>>>>
>>>>>>
>>>>>>> - clientLogin aka OpenAuth using
>>>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>>>>>>> been the default setting for pidgin releases since 2009
>>>>>>>
>>>>>>
>>>>>  This login path will stay but you need to update the DistID
>>>>> and DevID. We will give you a new set.
>>>>>
>>>>>>
>>>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and D

Re: AIM login

[Adium]

Just got a response from him this afternoon. Following up.

-Eric

Sent from my iPhone

> On Mar 13, 2017, at 4:38 PM, Robert Vehse  wrote:
> 
> Hi,
> 
> […]
> 
>> By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. I 
>> thought slogin.oscar.aol.com was supposed to die at the end of this month. I 
>> think that's breaking adium (mac OS X pidgin derivative) and we still 
>> haven't managed to contact their devs to fix it. So what is the fate of 
>> slogin supposed to be?
> 
> As far as I know Eric, Adium's Project Manager 
> (https://trac.adium.im/wiki/edr1084), has tried to contact Donald Le via 
> email on multiple occasions but hasn't received a response yet.
> 
> Regards,
> Robbie
> ___
> Devel mailing list
> de...@pidgin.im
> https://pidgin.im/cgi-bin/mailman/listinfo/devel

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Robert Vehse]

Hi,

[…]

> By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. I 
> thought slogin.oscar.aol.com was supposed to die at the end of this month. I 
> think that's breaking adium (mac OS X pidgin derivative) and we still haven't 
> managed to contact their devs to fix it. So what is the fate of slogin 
> supposed to be?

As far as I know Eric, Adium's Project Manager 
(https://trac.adium.im/wiki/edr1084), has tried to contact Donald Le via email 
on multiple occasions but hasn't received a response yet.

Regards,
Robbie
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[dequis]

" with distid 1502 which doesn't match any client we own,
>>> and we don't know how you found that one.
>>>
>>> So for the sake of avoiding a roundtrip in our communication and getting
>>> the release packaged ASAP, we went ahead and used the remaining 1718 distid
>>> for finch.
>>>
>>> This looks like it was a mistake, since we're now getting "Method not
>>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>>
>>> Did the 1718 distid get invalidated? Can you re-enable it so that we
>>> don't have to make another release?
>>>
>>> Thanks
>>>
>>> On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:
>>>
>>>> All,
>>>>
>>>> My comments are inline.
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> *Donald Le*
>>>> *Tech Director | Product Management and Support AIM Platform*
>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>> <%28703%29%20678-1073>
>>>> *AIM*: donald...@teamaol.com
>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>
>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>> integration, the date is tbd.
>>>>> I will answer your questions in the coming weeks.
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>> *Donald Le*
>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>>>> <%28703%29%20678-1073>
>>>>> *AIM*: donald...@teamaol.com
>>>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>>>
>>>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>>>>
>>>>>> 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
>>>>>>
>>>>>
>>>>  All DistID used for login.oscar.aol.com and
>>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM client
>>>> upgrade will start Feb 24th 2017.
>>>>
>>>>>
>>>>>> - clientLogin aka OpenAuth using
>>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>>>>>> been the default setting for pidgin releases since 2009
>>>>>>
>>>>>
>>>>  This login path will stay but you need to update the DistID
>>>> and DevID. We will give you a new set.
>>>>
>>>>>
>>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced
>>>>>> in
>>>>>> pidgin 2.11.0, released four months ago.
>>>>>>
>>>>>
>>>>  Same as above with OpenAuth.
>>>>
>>>>>
>>>>>> 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.
>>>>>>
>>>>>
>>>>  If Pidgin uses DistID = 1502 or 0, the login will be blocked.
>>>>
>>>>>
>>>>>> 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?
>>>>>>
>>>>>
>>>>  Yes.
>>>>
>>>>>
>>>>>> We're currently using these:
>>>>>>
>>>>>> Pidgin
>>>>>> DistID: 1550
>>>>>>

Re: AIM login

[Donald Le]

stID used for login.oscar.aol.com and
>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM client
>>> upgrade will start Feb 24th 2017.
>>>
>>>>
>>>>> - clientLogin aka OpenAuth using
>>>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>>>>> been the default setting for pidgin releases since 2009
>>>>>
>>>>
>>>  This login path will stay but you need to update the DistID and
>>> DevID. We will give you a new set.
>>>
>>>>
>>>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in
>>>>> pidgin 2.11.0, released four months ago.
>>>>>
>>>>
>>>  Same as above with OpenAuth.
>>>
>>>>
>>>>> 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.
>>>>>
>>>>
>>>  If Pidgin uses DistID = 1502 or 0, the login will be blocked.
>>>
>>>>
>>>>> 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?
>>>>>
>>>>
>>>  Yes.
>>>
>>>>
>>>>> We're currently using these:
>>>>>
>>>>> Pidgin
>>>>> DistID: 1550
>>>>> DevID: ma1cSASNCKFtrdv9
>>>>>
>>>>
>>>  I reached out to Pidgin, see below.
>>>
>>> From: Donald Le <donald...@teamaol.com>
>>> Date: Thu, Sep 22, 2016 at 6:20 PM
>>> Subject: Re: AIM login
>>> To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin Support
>>> List <support@pidgin.im>
>>>
>>> new DevID = do1UCeb5gNqxB1S1
>>> new distID = 1715
>>>
>>>
>>>>> Finch:
>>>>> DistID: 1552
>>>>> DevID: ma19sqWV9ymU6UYc
>>>>>
>>>>
>>>  No usage since August 2014 so no need new DistID and DevID.
>>>
>>>>
>>>>> Libpurple:
>>>>> DistID: 1553
>>>>> DevID: ma15d7JTxbmVG-RP
>>>>>
>>>>
>>>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>>>
>>> I found another Libpurple
>>> DistID: 1502 with no DevID >> new DistID = 1718, new DevID =
>>> ma18nmEklXMR7Cj_
>>>
>>>>
>>>>> 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

Re: AIM login

[dequis]

Hey Donald!

As you may have heard we already released pidgin 2.12.0 (together with
libpurple and finch 2.12.0), updating the distid/devids.

Here's what we used:

Pidgin:
Distid: 1715
Devid: do1UCeb5gNqxB1S1

Libpurple:
Distid: 1717
Devid: ma19CwYN9i9Mw5nY

Finch:
Distid: 1718
Devid: ma18nmEklXMR7Cj_

The first two are normal.

The third said in the original email "No usage since August 2014 so no need
new DistID and DevID", which is clearly wrong. There's also that "another
libpurple" with distid 1502 which doesn't match any client we own, and we
don't know how you found that one.

So for the sake of avoiding a roundtrip in our communication and getting
the release packaged ASAP, we went ahead and used the remaining 1718 distid
for finch.

This looks like it was a mistake, since we're now getting "Method not
allowed - clientLogin Not Allowed for this devId" errors in finch.

Did the 1718 distid get invalidated? Can you re-enable it so that we don't
have to make another release?

Thanks

On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:

> All,
>
> My comments are inline.
>
> Thanks,
>
>
> *Donald Le*
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>
> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com> wrote:
>
>> All,
>>
>> Quick update: we had to delay AIM client upgrade due to other
>> integration, the date is tbd.
>> I will answer your questions in the coming weeks.
>>
>>
>> Thanks,
>>
>>
>> *Donald Le*
>> *Tech Director | Product Management and Support AIM Platform*
>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>> <%28703%29%20678-1073>
>> *AIM*: donald...@teamaol.com
>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>
>> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>>
>>> 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
>>>
>>
>  All DistID used for login.oscar.aol.com and slogin.oscar.aol.com
> will be blocked. The date is tbd and AIM client upgrade will start Feb 24th
> 2017.
>
>>
>>> - clientLogin aka OpenAuth using
>>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>>> been the default setting for pidgin releases since 2009
>>>
>>
>  This login path will stay but you need to update the DistID and
> DevID. We will give you a new set.
>
>>
>>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in
>>> pidgin 2.11.0, released four months ago.
>>>
>>
>  Same as above with OpenAuth.
>
>>
>>> 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.
>>>
>>
>  If Pidgin uses DistID = 1502 or 0, the login will be blocked.
>
>>
>>> 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?
>>>
>>
>  Yes.
>
>>
>>> We're currently using these:
>>>
>>> Pidgin
>>> DistID: 1550
>>> DevID: ma1cSASNCKFtrdv9
>>>
>>
>  I reached out to Pidgin, see below.
>
> From: Donald Le <donald...@teamaol.com>
> Date: Thu, Sep 22, 2016 at 6:20 PM
> Subject: Re: AIM login
> To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin Support
> List <support@pidgin.im>
>
> new DevID = do1UCeb5gNqxB1S1
> new distID = 1715
>
>
>>> Finch:
>>> DistID: 1552
>>> DevID: ma19sqWV9ymU6UYc
>>>
>>
>  No usage since August 2014 so no need new DistID and DevID.
>
>>
>>> Libpurple:
>>> DistID: 1553
>>> DevID: ma15d7JTxbmVG-RP
>>>
>>
>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>
> I found another Libpurple
> DistID: 1502 with no DevID >> new DistID = 1718, new DevID =
> ma18nmEk

Re: AIM login

[Donald Le]

All,

My comments are inline.

Thanks,


*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com> wrote:

> All,
>
> Quick update: we had to delay AIM client upgrade due to other integration,
> the date is tbd.
> I will answer your questions in the coming weeks.
>
>
> Thanks,
>
>
> *Donald Le*
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
> <%28703%29%20678-1073>
> *AIM*: donald...@teamaol.com
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>
> On Fri, Oct 14, 2016 at 2:58 AM, dequis <d...@dxzone.com.ar> wrote:
>
>> 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
>>
>
 All DistID used for login.oscar.aol.com and slogin.oscar.aol.com
will be blocked. The date is tbd and AIM client upgrade will start Feb 24th
2017.

>
>> - clientLogin aka OpenAuth using
>> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
>> been the default setting for pidgin releases since 2009
>>
>
 This login path will stay but you need to update the DistID and
DevID. We will give you a new set.

>
>> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in
>> pidgin 2.11.0, released four months ago.
>>
>
 Same as above with OpenAuth.

>
>> 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.
>>
>
 If Pidgin uses DistID = 1502 or 0, the login will be blocked.

>
>> 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?
>>
>
 Yes.

>
>> We're currently using these:
>>
>> Pidgin
>> DistID: 1550
>> DevID: ma1cSASNCKFtrdv9
>>
>
 I reached out to Pidgin, see below.

From: Donald Le <donald...@teamaol.com>
Date: Thu, Sep 22, 2016 at 6:20 PM
Subject: Re: AIM login
To: Richard Vickery <r...@sfu.ca>, pid...@alexoren.com, Pidgin Support List
<support@pidgin.im>

new DevID = do1UCeb5gNqxB1S1
new distID = 1715


>> Finch:
>> DistID: 1552
>> DevID: ma19sqWV9ymU6UYc
>>
>
 No usage since August 2014 so no need new DistID and DevID.

>
>> Libpurple:
>> DistID: 1553
>> DevID: ma15d7JTxbmVG-RP
>>
>
 new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY

I found another Libpurple
DistID: 1502 with no DevID >> new DistID = 1718, new DevID =
ma18nmEklXMR7Cj_

>
>> 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

Re: AIM login

[Donald Le]

All,

Quick update: we had to delay AIM client upgrade due to other integration,
the date is tbd.
I will answer your questions in the coming weeks.


Thanks,


*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Fri, Oct 14, 2016 at 2:58 AM, dequis  wrote:

> 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  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 
> >
> > ___
> > 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

Re: AIM login

[dequis]

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  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 
>
> ___
> 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

Re: AIM login

[Gary Kramlich]

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 

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Donald Le]

Richard, Ethan,

Any update?

Thanks,


*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Thu, Sep 22, 2016 at 6:20 PM, Donald Le  wrote:

>
> new DevID = do1UCeb5gNqxB1S1
> new distID = 1715
>
> They will be ready to use after 1/2 hour.
>
> Thanks,
>
>
> *Donald Le*
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>
> On Thu, Sep 22, 2016 at 6:06 PM, Ethan Blanton  wrote:
>
>> Donald Le spake unto us the following wisdom:
>> > Who should I send the DevID and distID? or if you don't mind I deliver
>> it
>> > here?
>>
>> The list is fine.  It will necessarily be included in our public
>> source code anyway, so it might as well go to the list.
>>
>> > I don't know exactly what did you get from us to built AIM connectivity
>> in
>> > your Pidgin client.
>>
>> Very little.  Our OSCAR support was an effort of reverse engineering
>> many years ago, both on the part of Pidgin developers (most of whom
>> have left the project) and other third-party IM clients.
>>
>> > OpenAuth path is https://api.screenname.aol.com/auth/clientLogin.
>> > AIM Legacy 7.5.x  login path is kdc.uas.aol.com port 443.
>> >
>> > Please suggest 2 date/time for a quick call.
>>
>> Gary, can you tap someone (who will be around) for this?  If Mark is
>> available, I think he's worked on OSCAR most recently in any sort of
>> depth.
>>
>> Ethan
>>
>
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[pidgin]

On 23-09-2016 14:39, APB wrote:


On 09/21/2016 01:29 PM, pid...@alexoren.com wrote:

On 21-09-2016 10:47, Donald Le wrote:

I'd need a point of contact at Pidgin for AIM update that would
block users from login to AIM.


The hell?


He's saying that the heavy hand of Big Cousin (of Big Brother of
course) is requesting help blocking the usage of AIM.  I vote to VETO
the request... in case anyone is counting votes :)  Of course with
suitable compensation (say no less than $1 million USD) from AOL, the
requester might sway my opinion... not that my opinion has any sway
here.  Just food for thought.


That's what I thought at first, thus my reaction.

It turned out that AOL is planning a breaking change to the protocol and Donald 
is reaching out to Pidgin developers and offering to work with them (for free) 
to ensure a painless transition.

Donald, if you are reading this, please accept my apology.

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[APB]

On 09/21/2016 01:29 PM, pid...@alexoren.com wrote:

On 21-09-2016 10:47, Donald Le wrote:

To whom it may concern,

I'd need a point of contact at Pidgin for AIM update that would block 
users from login to AIM.


Thanks,

*Donald Le
*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com *
*
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166


The hell?


He's saying that the heavy hand of Big Cousin (of Big Brother of course) 
is requesting help blocking the usage of AIM.  I vote to VETO the 
request... in case anyone is counting votes :)  Of course with suitable 
compensation (say no less than $1 million USD) from AOL, the requester 
might sway my opinion... not that my opinion has any sway here.  Just 
food for thought.


- APB

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Donald Le]

new DevID = do1UCeb5gNqxB1S1
new distID = 1715

They will be ready to use after 1/2 hour.

Thanks,


*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Thu, Sep 22, 2016 at 6:06 PM, Ethan Blanton  wrote:

> Donald Le spake unto us the following wisdom:
> > Who should I send the DevID and distID? or if you don't mind I deliver it
> > here?
>
> The list is fine.  It will necessarily be included in our public
> source code anyway, so it might as well go to the list.
>
> > I don't know exactly what did you get from us to built AIM connectivity
> in
> > your Pidgin client.
>
> Very little.  Our OSCAR support was an effort of reverse engineering
> many years ago, both on the part of Pidgin developers (most of whom
> have left the project) and other third-party IM clients.
>
> > OpenAuth path is https://api.screenname.aol.com/auth/clientLogin.
> > AIM Legacy 7.5.x  login path is kdc.uas.aol.com port 443.
> >
> > Please suggest 2 date/time for a quick call.
>
> Gary, can you tap someone (who will be around) for this?  If Mark is
> available, I think he's worked on OSCAR most recently in any sort of
> depth.
>
> Ethan
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Ethan Blanton]

Donald Le spake unto us the following wisdom:
> Who should I send the DevID and distID? or if you don't mind I deliver it
> here?

The list is fine.  It will necessarily be included in our public
source code anyway, so it might as well go to the list.

> I don't know exactly what did you get from us to built AIM connectivity in
> your Pidgin client.

Very little.  Our OSCAR support was an effort of reverse engineering
many years ago, both on the part of Pidgin developers (most of whom
have left the project) and other third-party IM clients.

> OpenAuth path is https://api.screenname.aol.com/auth/clientLogin.
> AIM Legacy 7.5.x  login path is kdc.uas.aol.com port 443.
> 
> Please suggest 2 date/time for a quick call.

Gary, can you tap someone (who will be around) for this?  If Mark is
available, I think he's worked on OSCAR most recently in any sort of
depth.

Ethan

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Donald Le]

Ethan, Richard,

Thanks for the reply, I was choked but I am OK now :)

Who should I send the DevID and distID? or if you don't mind I deliver it
here?
I don't know exactly what did you get from us to built AIM connectivity in
your Pidgin client.

OpenAuth path is https://api.screenname.aol.com/auth/clientLogin.
AIM Legacy 7.5.x  login path is kdc.uas.aol.com port 443.

Please suggest 2 date/time for a quick call.


Thanks,



*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Thu, Sep 22, 2016 at 11:41 AM, Richard Vickery <r...@sfu.ca> wrote:

>
>   Original Message
> From: Ethan Blanton
> Sent: Wednesday, September 21, 2016 20:21
> To: Richard Vickery
> Reply To: Ethan Blanton
> Cc: pid...@alexoren.com; support@pidgin.im; Donald Le
> Subject: Re: AIM login
>
> Richard Vickery spake unto us the following wisdom:
> > Your "point of contact" is your company's IT department; we are
> > merely volunteers. Are you aware of the term "open source"?‎
>
> I realize you retracted this comment, but this sort of thing is
> becoming common (again) on this list. This comment is not directed
> entirely at you, you simply have the misfortune of being my example.
>
> Users, please do not take it upon yourselves to "defend" Pidgin or
> Pidgin developers. We are perfectly capable of doing so ourselves.
> Most indignant user responses like this that arrive on the list are
> misplaced.
>
> In this case, AOL has reached out to us, proactively, to notify us of
> a change in the protocol that is going to affect Pidgin and libpurple
> users. Asking for a specific point of contact to work through this is
> a VERY reasonable thing to do. AOL's engineers are paid, and spending
> time with a dedicated Pidgin developer at an established time is the
> best use of everyone involved's time and effort.
>
> I suspect this specific comment was a reaction to the language, not
> the content, and that is why it was retracted. However, rude
> responses to other corporate employees are not necessary, either; I
> have, for example, a form response that I send to confused Oracle
> employes that is much more useful and helpful than the snark often
> sent by list members -- particularly list members who have to have
> seen my rote response multiple times, and do not even include the help
> desk URL it contains.
>
> This is a community. I often send impatient and brusque emails,
> myself (the archives are proof of that), but I do try to direct them
> at those who deserve it. Please do the same!
>
> Ethan
>
> Thanks Ethan,
>
> This is very useful‎! My retraction was actually because my comment was
> late by at least 15 minutes even before I began reading what I was replying
> to and other more useful replies - where mine was completely useless, both
> in tone and content - were posted. Although I would like to point out, in
> defence, that if comments similar in content had not been made in the past,
> likely at least started by developers, my comments would never be made.
>
> My apologies,
>
> Richard
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Richard Vickery]

  Original Message  
From: Ethan Blanton
Sent: Wednesday, September 21, 2016 20:21
To: Richard Vickery
Reply To: Ethan Blanton
Cc: pid...@alexoren.com; support@pidgin.im; Donald Le
Subject: Re: AIM login

Richard Vickery spake unto us the following wisdom:
> Your "point of contact" is your company's IT department; we are
> merely volunteers. Are you aware of the term "open source"?‎

I realize you retracted this comment, but this sort of thing is
becoming common (again) on this list. This comment is not directed
entirely at you, you simply have the misfortune of being my example.

Users, please do not take it upon yourselves to "defend" Pidgin or
Pidgin developers. We are perfectly capable of doing so ourselves.
Most indignant user responses like this that arrive on the list are
misplaced.

In this case, AOL has reached out to us, proactively, to notify us of
a change in the protocol that is going to affect Pidgin and libpurple
users. Asking for a specific point of contact to work through this is
a VERY reasonable thing to do. AOL's engineers are paid, and spending
time with a dedicated Pidgin developer at an established time is the
best use of everyone involved's time and effort.

I suspect this specific comment was a reaction to the language, not
the content, and that is why it was retracted. However, rude
responses to other corporate employees are not necessary, either; I
have, for example, a form response that I send to confused Oracle
employes that is much more useful and helpful than the snark often
sent by list members -- particularly list members who have to have
seen my rote response multiple times, and do not even include the help
desk URL it contains.

This is a community. I often send impatient and brusque emails,
myself (the archives are proof of that), but I do try to direct them
at those who deserve it. Please do the same!

Ethan

Thanks Ethan, 

This is very useful‎! My retraction was actually because my comment was late by 
at least 15 minutes even before I began reading what I was replying to and 
other more useful replies - where mine was completely useless, both in tone and 
content - were posted. Although I would like to point out, in defence, that if 
comments similar in content had not been made in the past, likely at least 
started by developers, my comments would never be made.

My apologies, 

Richard

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Richard Vickery]

Sent from my BlackBerry 10 smartphone.
  Original Message  
From: Richard Vickery
Sent: Wednesday, September 21, 2016 19:43
To: pid...@alexoren.com; support@pidgin.im; Donald Le
Reply To: Richard Vickery
Subject: Re: AIM login



Sent from my BlackBerry 10 smartphone.
  Original Message  
From: pid...@alexoren.com
Sent: Wednesday, September 21, 2016 13:30
To: support@pidgin.im
Reply To: pid...@alexoren.com
Subject: Re: AIM login

On 21-09-2016 10:47, Donald Le wrote:
> To whom it may concern,
>
> I'd need a point of contact at Pidgin for AIM update that would block users 
> from login to AIM.
>
> Thanks,
>
> *Donald Le
> *
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com <mailto:donald...@teamaol.com>*
> *
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

The hell?

Your "point of contact" is your company's IT department; we are merely 
volunteers. Are you aware of the term "open source"?‎


Sorry. Please ignore this contribution.‎

___
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

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Richard Vickery]

Sent from my BlackBerry 10 smartphone.
  Original Message  
From: pid...@alexoren.com
Sent: Wednesday, September 21, 2016 13:30
To: support@pidgin.im
Reply To: pid...@alexoren.com
Subject: Re: AIM login

On 21-09-2016 10:47, Donald Le wrote:
> To whom it may concern,
>
> I'd need a point of contact at Pidgin for AIM update that would block users 
> from login to AIM.
>
> Thanks,
>
> *Donald Le
> *
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com <mailto:donald...@teamaol.com>*
> *
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

The hell?

Your "point of contact" is your company's IT department; we are merely 
volunteers. Are you aware of the term "open source"?‎


___
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

Re: AIM login

[Donald Le]

My answers are inline.

Thanks,


*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Wed, Sep 21, 2016 at 6:22 PM, Ethan Blanton  wrote:

> Donald Le spake unto us the following wisdom:
> > We will sunset the authorizers login.oscar.aol.com and
> slogin.oscar.aol.com
> > used by your clients today.
> > Notes: 53809 unique logins in July 2016, 54003 in August 2016 and 50810
> to
> > date in September 2016.
>
> I believe we only use these when people have trouble using a method we
> call "clientLogin" that uses login.messaging.aol.com.  I'm not sure if
> this is the same or not.
>
 It's the same.

>
> > Your client has a distID = 0 and "no" DevID. The new authentication path
> > requires a valid distID and DevID.
>
> I believe that this is because we have tried multiple times to get IDs
> and were unable to get in contact with anyone who could/would issue
> them to us.
>
 I will create them and send by COB tomorrow the latest.

>
> Note that libpurple (the IM communication library underlying Pidgin)
> is used by multiple clients, and this may affect this issuance.
>
> > We will upgrade our AIM client (Legacy, Web and Mobile) in the coming
> month.
>
> We appreciate the heads up, although more lead time would of course
> have been easier to coordinate.
>
 The update will start Oct 17th and I can delay 2 weeks for Pidgin.

>
> I will be mostly unavailable over the next few weeks, so hopefully
> another developer can schedule a conference call.
>
> Ethan
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Ethan Blanton]

Donald Le spake unto us the following wisdom:
> We will sunset the authorizers login.oscar.aol.com and slogin.oscar.aol.com
> used by your clients today.
> Notes: 53809 unique logins in July 2016, 54003 in August 2016 and 50810 to
> date in September 2016.

I believe we only use these when people have trouble using a method we
call "clientLogin" that uses login.messaging.aol.com.  I'm not sure if
this is the same or not.

> Your client has a distID = 0 and "no" DevID. The new authentication path
> requires a valid distID and DevID.

I believe that this is because we have tried multiple times to get IDs
and were unable to get in contact with anyone who could/would issue
them to us.

Note that libpurple (the IM communication library underlying Pidgin)
is used by multiple clients, and this may affect this issuance.

> We will upgrade our AIM client (Legacy, Web and Mobile) in the coming month.

We appreciate the heads up, although more lead time would of course
have been easier to coordinate.

I will be mostly unavailable over the next few weeks, so hopefully
another developer can schedule a conference call.

Ethan

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

[Donald Le]

Hi Eion,

We will sunset the authorizers login.oscar.aol.com and slogin.oscar.aol.com
used by your clients today.
Notes: 53809 unique logins in July 2016, 54003 in August 2016 and 50810 to
date in September 2016.

Your client has a distID = 0 and "no" DevID. The new authentication path
requires a valid distID and DevID.

We will upgrade our AIM client (Legacy, Web and Mobile) in the coming month.

Let's have a conference call to go over the AIM update. Please suggest 2
date/time.


Thanks,



*Donald Le*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

On Wed, Sep 21, 2016 at 4:39 PM, Eion Robb  wrote:

> Hi Donald,
>
> If this is related to the development of Pidgin then the development
> mailing list (cc'd) would be the best place to get in touch.
>
> This AIM update sounds troubling.  Do you have docs and/or a timeline
> around this?
>
> Cheers,
> Eion
>
> On 22 September 2016 at 02:47, Donald Le  wrote:
>
>> To whom it may concern,
>>
>> I'd need a point of contact at Pidgin for AIM update that would block
>> users from login to AIM.
>>
>> Thanks,
>>
>>
>> *Donald Le*
>> *Tech Director | Product Management and Support AIM Platform*
>> *O*: 703-265-5645 | *M*: 703-678-1073
>> *AIM*: donald...@teamaol.com
>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>
>> ___
>> 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

Re: AIM login

[Eion Robb]

Hi Donald,

If this is related to the development of Pidgin then the development
mailing list (cc'd) would be the best place to get in touch.

This AIM update sounds troubling.  Do you have docs and/or a timeline
around this?

Cheers,
Eion

On 22 September 2016 at 02:47, Donald Le  wrote:

> To whom it may concern,
>
> I'd need a point of contact at Pidgin for AIM update that would block
> users from login to AIM.
>
> Thanks,
>
>
> *Donald Le*
> *Tech Director | Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com
> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>
> ___
> 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

Re: AIM login

[pidgin]

On 21-09-2016 10:47, Donald Le wrote:

To whom it may concern,

I'd need a point of contact at Pidgin for AIM update that would block users 
from login to AIM.

Thanks,

*Donald Le
*
*Tech Director | Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com *
*
*AOL Inc*. 22070 Broderick Drive Dulles, VA 20166


The hell?


___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support