-
Notifications
You must be signed in to change notification settings - Fork 0
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
Confused about install + setup. #1
Comments
So yes, as mentioned you first run |
Thanks I am getting this error when running the final step -
|
Hello @nullwriter I have managed to get this going :) Now the app is running and I have the below output in console:
I have registered my number with whatsapp too, so now how do I interact with the crypto bot? Also have you seen the issues with Any ideas on how to best go around this, maybe a new UI to this app is needed - some simple REST interface to the BOT? |
You interact by opening a conversation in Whatsapp with the number of the bot. Make sure to add it to your contact list first. I have seen those issues and it's something that happens since Whatsapp does not allow 3rd party applications to work with them. But I've found that a sweet spot to make it pass as a normal user is giving it a delay which is included in the code here (after 3 different numbers banned :) ). When the bot replies too quickly, it becomes flagged and banned. |
@nullwriter when I was testing on my local with my number all was fine. I bought a new number and loaded into Google Cloud and the number was blocked right after the first reply to HELP command :( When you say the delay in the code is the the 10 sec loop in |
@nullwriter I have looked more in the code and found |
Hey @ydennisy, sorry for the delay, I've been away but back now. Been doing some research and it seems Whatsapp has upped their game in detecting bots. From reading several issues in Yowsup, I've found what seems to be the key to surpass their bot tests. Below is a copy paste of a comment 7 days ago where the guy tested several methods and came to a conclusion: 1 - If you register a number directly via yowsup, the number is banned after one message (tested with 3 numbers) 2 - If you register a phone in your android, chat a bit, and then, after 12 - 14h you close whatsapp client and register the number on yowsup, it works. 3 - ONLY ONE TEST: 72h after registration on Android, and created profile via WApp Web, it fully worked for two weeks until I sent a friend one link that was banned in FB (and I didn't know). |
In the following days I'll be testing this and updating, if needed, the code. |
Hello @nullwriter ! I'm the guy that wrote your copypaste. Further tests made: It's important to register having modified the env_android.py (and recompiled) with this data: _MD5_CLASSES = "YlajJPPGUUP1Ptcic2XKNA==" _VERSION = "2.18.105" Yesterday I burned three phone numbers at 6-10 messages, and with this method I've been able to send 85 this morning (and received answer from myself). The key of all this mess is that yowsup get fixed so that it can send messages with -E android. I don't know python nor the API; and I code in C#, so I can't help. But I'm doing my best to deduce as a tester what the problem is; and I think it's this. |
This is my original comment: |
Hello,
Is the process first to get the app running using
docker-compose
and then register onyowsup
, make changes to thecreds
file and run the second docker command?Is the app accessible at any URL?
Thanks in advance.
Dennis
The text was updated successfully, but these errors were encountered: