nother release?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>> On 27 January 2017 at 01:54, Donald Le <donald...@teamaol.com> wrote:
>>>>>>>>> All,
>>
;
>>>>>>>
>>>>>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le <donald...@teamaol.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> All,
>>>>>>>>
>>>>>>>> Qu
t;>>>>
>>>>>>>> All,
>>>>>>>>
>>>>>>>> Quick update: we had to delay AIM client upgrade due to other
>>>>>>>> integration, the date is tbd.
>>>>>>>> I will answer your ques
t;>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>> *Donald Le*
>>>>>>> *Tech Director | Product Management and Support AIM Platform*
>>>>>>> *O*: 703-265-5645 <%28703%29%20265-5645> |
gt;>>
>>>>>>> Hi, I have a couple of questions, since there may have been a
>>>>>>> misunderstanding here.
>>>>>>>
>>>>>>> Pidgin currently supports three auth methods for AIM:
>>>>>>>
>>
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
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
; 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.screennam
ses 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. Int
t; 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
>
t 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 t
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*:
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
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
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
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
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
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
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
gin.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
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&
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
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 nee
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
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
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
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*:
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
Hi. After I enter my login information for AIM and hit sign-on I get a
prompt that says: See attached picture.
--
Floating in the Stratosphere,
Derek DJ
Working Towards A Better Tomorrow
attachment: AIM Login Issue.png___
Support@pidgin.im mailing
On 06/17/2010 05:48 PM, Derek Jaughn wrote:
Hi. After I enter my login information for AIM and hit sign-on I get a
prompt that says: See attached picture.
Rather than attaching a image, which some people may not want to open,
you're probably better off simply typing the error. This was
31 matches
Mail list logo