Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

socialprovider.js needs a better way to identify it's own resource id #21

Open
dborkan opened this issue Apr 9, 2014 · 2 comments
Open
Labels

Comments

@dborkan
Copy link
Contributor

dborkan commented Apr 9, 2014

XMPPSocialProvider's onMessage method had been checking the message to see if it the this.loginOpts.agent string ('chatdemo') was found. This is not working properly for GoogleTalk.

For example, if I sign into the chatdemo as [email protected], chatdemo expects my fullJID to be [email protected]/chatdemo, however replies (from a buddy using googletalk within gmail) are actually going to [email protected]/9FD5E48D. We need a way to identify that this "9FD5E48D" id matches our instance of chatdemo.

@iislucas iislucas added the bug label Apr 11, 2014
@dborkan dborkan closed this as completed Apr 23, 2014
@dborkan dborkan reopened this Apr 23, 2014
@willscott
Copy link
Member

The right way to do it if support would be exposing the sw via capabilities:
http://www.xmpp.org/extensions/xep-0115.html

@willscott
Copy link
Member

It would also be worth seeing if there is the ability to detect presence through deniable means.

Something like a random nonce fitting an elliptic curve used by http://telex.cc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants