41–49 of 49 posts
why hasn't there been anything like this for iMessage? or any 3rd party applications at all, really.
https://neosmart.net/blog/2018/imessage-for-windows/
Taking full advantage of UWP features and functionality.
Earlier quoted context omitted.
One alternative is sandboxing the js code (or using existing browser or networking logging capabilities) to reverse engineer network requests and write a more raw client instead of piggybacking onto the web client, that would still have risks of changes but less likely than this.
> reverse engineer network requests and write a more raw client People already have done that. The most famous example is the yowsup [1] python library. The problem with these client implementations is that WhatsApp is banning any numbers that use them [2]. So most recent attempts to use WhatsApp outside of the official clients revolve around using WhatsApp Web somehow. That appears to work better, but even here if y…
Earlier quoted context omitted.
> reverse engineer network requests and write a more raw client People already have done that. The most famous example is the yowsup [1] python library. The problem with these client implementations is that WhatsApp is banning any numbers that use them [2]. So most recent attempts to use WhatsApp outside of the official clients revolve around using WhatsApp Web somehow. That appears to work better, but even here if y…
How can the server component of WhatsApp tell that the client is using the Python library you mention? If that library implements the protocol correctly, shouldn't it be indistinguishable from the official web client to the server?
https://github.com/tgalal/yowsup/blob/master/yowsup/env/env_...
why hasn't there been anything like this for iMessage? or any 3rd party applications at all, really.
I created a native iMessage app for Windows 10: https://neosmart.net/blog/2018/imessage-for-windows/ Taking full advantage of UWP features and functionality.
Earlier quoted context omitted.
> reverse engineer network requests and write a more raw client People already have done that. The most famous example is the yowsup [1] python library. The problem with these client implementations is that WhatsApp is banning any numbers that use them [2]. So most recent attempts to use WhatsApp outside of the official clients revolve around using WhatsApp Web somehow. That appears to work better, but even here if y…
3rd party implementations, such as that python library, have two fundamental issues (beyond what's mentioned here). 1) They're using outdated versions of the protocols, which they won't be motiviated to fix until those old versions are cut off server-side and their implementation suddenly stops working. 2) They never quite figured out how to correctly handle all the nuances and corner cases of the E2E encryption, so…
I've never used one of these products, so I might be wrong, but as far as I understood it, the way WhatsApp bans your phone number if you use a third party client is done in a way that is permanent? So instead of saying "sorry your version is too old please use a newer one" they say "sorry your version is too old we don't want to see you ever again even if you fix it". It's totally okay to do something like "sorry the version is too old" if it's not your number that's banned but the outdated protocol implementation.
> the maintainers have basically given up and abandoned the projects
Because WhatsApp is sending DMCA requests like crazy [1] and the constant protocol changes make it hard for third party developers. See the opinion by one dev here [2].
If WhatsApp came out with a public statement about supporting third party clients, listing their conditions, it would be really great progress. Matrix, IRC, etc all thrive with different client implementations, even Threema officially tolerates the OpenMittsu third party client. The official communication I've seen by WhatsApp is the opposite.
[1]: https://github.com/github/dmca/blob/332f1896902c4f5780a249c0...
[2]: https://github.com/Enrico204/Whatsapp-Desktop/commit/18ba8a4...
My solution was to run WhatsApp in emulator and enable adb over tcp and send adb commands from server directly to emulator. I automate sending messages and pdf files from our erp system. and for receiving messages we just have a Whatsapp web available for one of our employee so he can reply and escalate whatever.
What's a shame here is that the "WhatsApp Business API Client" [1] would actually be the perfect tool for personal projects like this. Unfortunately, its still being reserved for use by only larger businesses planning to use it at scale, so they can be meaningfully paying customers. Offering low-volume non-customer-facing free access to a product like this would likely make everyone here quite happy. [1]: https://dev…
https://developers.facebook.com/docs/whatsapp/faq
> For single-instance production server setup, we recommend at least 250 GB SSD, 16 GB RAM, and 4 core CPU.
https://www.facebook.com/business/m/whatsapp/business-api/
> In order to ensure a high quality experience for businesses and users, we're in a limited public preview. If you'd like to work with us, submit more information about your business for consideration as we continue to expand our availability.
I would like to move away from WhatsApp for privacy reasons and out of principle.
Could I use this to set an auto-reply message to users contacting me, redirecting them to my new messenger e.g. Signal?
Earlier quoted context omitted.
What's a shame here is that the "WhatsApp Business API Client" [1] would actually be the perfect tool for personal projects like this. Unfortunately, its still being reserved for use by only larger businesses planning to use it at scale, so they can be meaningfully paying customers. Offering low-volume non-customer-facing free access to a product like this would likely make everyone here quite happy. [1]: https://dev…
Indeed, it would be great to have something like this for non-business customers as well. Right now it's very much targeted at large businesses atm and seems to want a beefy computer, so you can't really install it on your RPI. https://developers.facebook.com/docs/whatsapp/faq > For single-instance production server setup, we recommend at least 250 GB SSD, 16 GB RAM, and 4 core CPU. https://www.facebook.com/business/…
The truth is that the product does not actually need much RAM, and storage is a direct function of the number of conversations and messages you're handling with the product. The main bottleneck is really just I/O for the databases. For the use cases of everyone here, it absolutely could run on an RPi. Easily.
Very nice project. I would like to move away from WhatsApp for privacy reasons and out of principle. Could I use this to set an auto-reply message to users contacting me, redirecting them to my new messenger e.g. Signal?