Open drook opened 8 years ago
Oh... sorry then. You're right, I was missing = at the end. Sorry for bothering.
By the way it looks like it's impossible to use XMPP gateway with running Whatsapp client on the phone: they start to interfere transwaht.py is gettin "Unauthorized" errors, and after rerequesting the code for a small number of retries (3) with WART I got ten(!) calls from Woodside, CA, United States. Didn't even want to be involved in a conversation of any kind with techsuppport. So, in case somebody will step on it, beware. Looks like it's suited only for mimicing a client from non-Andriod/non-IOS phone (although it's a great thing).
To use yowsup-based clients(transports) you need to extract password from the phone and use it with transport, requesting new password with WART disable other clients
Yes, but there are limited number of ways to do so: from 4 of the links in the Usage article three are dead: method described in the last one is marked as "doesn't work anymore", third one is 404, second one is wiped out by the author, so only first one remains, and it does look very similar to WART, so i thought....
As far as I know, whatsapp only allows one connection per account. Thus you cannot use the official whatsapp client and transwhat simultaneously. You can, however, connect to transwhat in gateway mode using multiple XMPP resources e.g. You run an XMPP client on your cellphone and your laptop and they both connect with the same account to a transwhat server.
@moyamo btw, this error appear when password not encoded properly, also there is a different problem - when password incorrect (but encoded ok) - transwhat is just crashed :)
I think this is related to https://github.com/stv0g/transwhat/issues/44
I'm trying to run transwhat as a spectrum2 backend. I've set up spectrum2 (it's running ICQtransport for two weeks now) and launched transwhat. I got my password from WART, registered to transport, and I'm getting the error below when trying to log in. I took a tcpdump capture, the connection is made successfully to the e1.whatsapp.net:443, and it's closing by the remote, so it looks like the data is transmitting fine.
Environment:
OS: FreeBSD 10-STABLE
Python:
Backend debug log: