Re: AIM login

[Eion Robb]

Hi Donald,

We've heard through a few of our support channels that you're still seeing
people not using the correct details when they're logging into AIM from
Pidgin.

Dequis emailed you last month with the urls that we're fetching that are
indeed showing distId=1715 and devId=do1UCeb5gNqxB1S1 - he also asked if
you could send through the details of your Pidgin version that you were
testing with.

Are you able to confirm which auth URLs we should be using so we can try
track down why you're not seeing the updated distId/devId?

Cheers,
Eion

On 14 March 2017 at 05:01, dequis  wrote:

> Hi, can confirm that finch is fixed now, thank you!
>
> That issue with pidgin 2.12.0 is really odd! I just tested both windows
> installers (online and offline) and they seem fine. We did have one user
> reporting a similar issue, but we couldn't reproduce it or explain it.
>
> Please verify the version with buddy list -> help menu -> about, the first
> line should say "Pidgin 2.12.0 (libpurple 2.12.0)" followed by "unknown".
> Also, help menu -> plugin information should say 2.12.0 for the AIM plugin.
> That kind of mixup is rare but who knows!
>
> You can also enable extra debug by opening cmd.exe and doing "set
> PURPLE_UNSAFE_DEBUG=1" before executing pidgin.
>
> Then open help menu -> debug window and connect the account. This is what
> I get:
>
> [...]
>> (12:27:52) certificate: Successfully verified certificate for
>> api.screenname.aol.com
>> (12:27:52) util: Request: 'POST /auth/clientLogin HTTP/1.0
>> Connection: close
>> Accept: */*
>> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
>> Content-Length: 85
>>
>> devId=do1UCeb5gNqxB1S1=xml=[password]=dx%40dxzone.com.ar'
>> (12:27:53) util: Response headers: 'HTTP/1.1 200 OK
>> [...]
>> (12:27:53) util: requested to fetch (https://api.oscar.aol.com/
>> aim/startOSCARSession?a=[access token]=1715=xml=
>> do1UCeb5gNqxB1S1=1489418868=1_sha256=[signature]), full=1,
>> user_agent=((null)), http11=0
>>
>
> So as far as I can see everything is fine. I hope that helps narrow it
> down.
>
> By the way, is the message supposed to be shown on every login from a
> legacy auth method? I don't see it when I intentionally set pidgin to
> connect to "login.oscar.aol.com" with "don't use encryption" and
> "MD5-based" - it just succeeds without complaining.
>
> 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?
>
> Thanks.
>
> On 13 March 2017 at 09:38, Donald Le  wrote:
>
>> Hi again,
>>
>> I download Pidgin 2.12.0 and test login.
>>
>> The "new" distID and devID were not used, and I received the upgrade
>> message.
>> The client is still on the old distID and NO devID.
>> Could you double-check?
>>
>> LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 08:02:11 2017  
>> bos_srv-l014bMon Mar 13 08:20:19 2017 bos_srv-l014b
>> LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 07:43:23 2017  
>> bos_srv-l014bMon Mar 13 07:49:22 2017 bos_srv-l014b
>>
>>
>> Thanks,
>>
>>
>> *Donald Le*
>> *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 Mon, Mar 13, 2017 at 7:33 AM, Donald Le  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  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 

Cannot uninstall Pidgin

[Cecilia Le]

Hello Pidgin support staff,

I'm having a little trouble uninstalling Pidgin. I received the following
screen when attempting to uninstall:

[image: Inline images 1]

More details:
- Windows 10
- Pidgin doesn't appear in the 'Apps and Features' list, thus cannot delete
that way
- I cut/pasted the program folder to move it from a folder I made in the
C:\ drive 'Program Files 2' to 'Program Files (x86), then moved it back
- I downloaded the Facebook .dll files, but then deleted them after
receiving this error screen (to no effect)

Please let me know if you require any further information.

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

Re: Problems logging on to facebook

[Shlomi Fish]

Hi Ms. Ross!

Please see the earlier discussions (search for "Facebook") here -
https://pidgin.im/pipermail/support/2017-March/thread.html . You need to
upgrade the plugin and it should be fine.

Regards,

Shlomi Fish


On Mon, 3 Apr 2017 10:44:16 +0100 Hannah Ross 
wrote:

> Hi all,
> 
> Recently switched computers and cannot get Pidgin to login to Facebook,
> getting error: Null value for $.viewer.message_threads.sync_sequence_id
> 
> On the other side Facebook is telling my account was logged in to from an
> unrecognised location, but although I've asked it to remember the device my
> Pidgin still isn't working.



-- 
-
Shlomi Fish   http://www.shlomifish.org/
Buffy Factoids - http://www.shlomifish.org/humour/bits/facts/Buffy/

I started out as a BASIC programmer. Some people would say that I’m
permanently damaged. Some people are undoubtedly right.
— Larry Wall

Please reply to list if it's a mailing list post - http://shlom.in/reply .

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

Re: Problems logging on to facebook

[Eion Robb]

Hi there,

You need to update the Facebook plugin to resolve this.

Cheers,
Eion

On 3 April 2017 at 21:44, Hannah Ross  wrote:

> Hi all,
>
> Recently switched computers and cannot get Pidgin to login to Facebook,
> getting error: Null value for $.viewer.message_threads.sync_sequence_id
>
> On the other side Facebook is telling my account was logged in to from an
> unrecognised location, but although I've asked it to remember the device my
> Pidgin still isn't working.
>
>
>
> ___
> 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: Unicode Not Working

[Eion Robb]

Hi there,

Pidgin can't use the windows alt-codes, but the GTK codes are working fine
here.  Are you getting the *u* character displaying on screen? If you
right-click on the message send text area thing, then go to the "Input
Methods" menu, is "Simple (system)" picked?

Cheers,
Eion

On 3 April 2017 at 21:08, Andrew Allen  wrote:

> Hello, I've been trying to get the latest version of Pidgin to accept
> unicode characters. I've tried both the standard windows Alt+ as well
> as the GTK CTRL+SHIFT+U and then the hexadecimal codes. I'm unsure what I
> should try next. Thank you kindly.
>
> ___
> 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

Problems logging on to facebook

[Hannah Ross]

Hi all,

Recently switched computers and cannot get Pidgin to login to Facebook,
getting error: Null value for $.viewer.message_threads.sync_sequence_id

On the other side Facebook is telling my account was logged in to from an
unrecognised location, but although I've asked it to remember the device my
Pidgin still isn't working.
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Unicode Not Working

[Andrew Allen]

Hello, I've been trying to get the latest version of Pidgin to accept 
unicode characters. I've tried both the standard windows Alt+ as 
well as the GTK CTRL+SHIFT+U and then the hexadecimal codes. I'm unsure 
what I should try next. Thank you kindly.


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

Re: freenode, identify with nickserv

[Olaf Hering]

On Thu, Feb 09, Olaf Hering wrote:

> There are various howtos on the Freenode website about automatically
> identify with NickServ during connect. However, pidgin is missing.
> Its not obvious how one would actually do that automation with pidgin.
> 
> Does anyone know how to do that, so their website can be updated to
> cover also pidgin?

As of now there are still no pidgin specific instructions in freenodes
documentation.

What seems to work for me, with 2.12.0:
- enable the irchelper.so plugin
- in the account settings for FreeNode, advanced tab:
  port: 6697
  enable SSL
  disable SASL (extra work needed for it)
  auth name: nickname used for NickServ
  nick password: nickpassword used for NickServ
  enable "Disconnect Ghosts"
  auto-join channels: #chanA, #chanB
- in the global settings for auto-join chats:
  channel: #chanA
  Group: Chats
  disable auto-join during connect
  enable "remain in channel if window is closed"

There is a race in the auto-join feature. IF the global one is used
channel join will happen before or while NickServ identification is
still in progress. Therefore each channel has to be configured in two
places.

This race may be avoided with the usage of SASL. But its unclear how to
configure it, due to lack of pidgin specific instructions at freenode.net.


Thanks.

Olaf


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