3 ms·
It’s not a library. It’s a distributed multi-node WhatsApp client that handles the proprietary parts and interacts with your chatbot application using webhooks/
by rescbr 5y ago
It’s not a library. It’s a distributed multi-node WhatsApp client that handles the proprietary parts and interacts with your chatbot application using webhooks/REST APIs.
Not trivial to setup and operate, as it was designed for high-throughput scenarios. It’s very understandable that smaller customers wouldn’t want to handle that little monster.
- jeltz 5y agoThat is exactly what I thought which is why I suggested that FB should replace their ugly hack with a normal library. But the person who I replied claimed they have a library which sounded weird to me because then there would be no ops problem. I feel FB is solving a technical problem by alienating a bunch of their users with a terms change. Why not instead just build the right technical solution?
- saurik 5y agoBy "library" I assumed you were just concerned with "local". I put it in quotes as it isn't a literal library that you would embed in your build system and link into your program. I honestly don't see how it being a literal library would make it easier... that frankly sounds more complex to integrate and maintain and ensure correct operation of than a separate daemon that you interact with over HTTP instead of some presumably-C-compatible ABI.