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

My advice #1

Closed
saade opened this issue Feb 20, 2019 · 1 comment
Closed

My advice #1

saade opened this issue Feb 20, 2019 · 1 comment

Comments

@saade
Copy link

saade commented Feb 20, 2019

I use this solution too (not yours but using Store).
If you plan to distribute this for any people on github, you should be aware that whatsapp can easily identify that you`re using Pupeteer for automation AND using the Store.

We use this method since 2017, and yes, using only as a chatbot, and still getting banned ...

An real-life example is MGP25 with his api, ( i know it connects directly to whatsapp servers and etc ). They know about him, whatsapp told about him in a anti-spam conference ...

So. If i was you, i would consider keeping this repository private, it garantees that this method will be available longer.

Dont read me wrong ;) as i said, just a advice

@pedroslopez
Copy link
Owner

Hello there!

Thanks for the insight! This was really meant as a proof of concept to see if (at least for now) I could get a WhatsApp client running that wasn't banned instantly. Of course, we'll probably never have a 100% undetectable way of doing bots or whatever it may be in a way that's relatively automated or whatnot, so I don't really expect this to be the end all and be all for unofficial WhatsApp client libraries.

I personally haven't been banned by using the method, but the fact of the matter is that, at least for the time being, WhatsApp doesn't allow us to make bots on the platform so we'll have to face the consequences of doing so. Regardless, good to know that the specific method in question could lead to a ban.

Thanks again for the heads up! Appreciate your comments.

pedroslopez added a commit that referenced this issue Feb 21, 2019
mpirescarvalho referenced this issue in mpirescarvalho/whatsapp-web.js Feb 2, 2021
Added Sticker author and sticker name support
mpirescarvalho referenced this issue in mpirescarvalho/whatsapp-web.js Feb 11, 2021
Added Sticker author and sticker name support
koodinikula pushed a commit to koodinikula/whatsapp-web.js that referenced this issue Oct 29, 2022
…/patch

Update WhatsApp Web Version (2.2234.13)
@devsakae devsakae mentioned this issue Nov 9, 2023
7 tasks
Belfio pushed a commit to Belfio/whatsapp-web.js that referenced this issue Jan 9, 2024
daviiRezende referenced this issue in daviiRezende/whatsapp-web.js Jun 7, 2024
fix(webpack-exodus): Bad export name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants