whatsapp-http-api
whatsapp-http-api copied to clipboard
devlikeapro
Connect `wppconnect` as new engine
https://github.com/wppconnect-team/wppconnect https://wppconnect.io/wppconnect/pages/getting-started/creating-client.html https://wppconnect.io/wppconnect/pages/getting-started/basic-functions.html
Hi! Do you miss any function in the current engines? If wpp gives more - we'd love to add it for sure!
https://wppconnect.io/wppconnect/classes/Whatsapp.html#sendLocation
Yes, it doesn't in the WEBJS engine(on sendLocation) https://github.com/devlikeapro/whatsapp-http-api/issues/102#issuecomment-1553842649
in NOWEB I am concerned about this
Working with the engine requires more attention, because it’s easy to be blocked with it!
https://waha.devlike.pro/docs/how-to/engines/#noweb
In view of the points addressed, it appears that WPPConnect may not be the most suitable replacement for NOWEB. My understanding, based on the documentation, is that WPPConnect, similar to Venon, operates as a browser-based integration, as does the default one.
If the original poster's concern pertains to potential blocking issues while using NOWEB, I would recommend considering other available engines. It's worth noting that the primary objective of NOWEB is to ensure a low footprint on server resources, rather than to offer the full range of features provided by its browser-based counterparts.
I strongly recommend to not work on this issue unless there is a feature that is unsupported by other engines already in place.
@arthurbarros the addition of a new engine does not mean that NOWEB is going to be removed or replaced, it will only be another engine available to those who need it or prefer it
@angeljqv thank you for pointing it out! No engines will be ever replaced or removed while its author supports it
Hi! Nothing so far :( If one's interested in that - I'll be happy to review the changes!
Interesting, the client and methods looks almost the same as venom one https://github.com/orkestral/venom They also provide their own HTTP API for the client, https://github.com/wppconnect-team/wppconnect-server
I'll try to install and run few tests a bit later, but if the project has the same problems as venom has (pretty slow loading, sending and receiving messages when you have a lot of incoming messages) - probably we won't add it as an engine...
I do love the idea of having a single HTTP API for all available engines tho, so we can switch between them without changing the application, business logic code :)
I do love the idea of having a single HTTP API for all available engines tho, so we can switch between them without changing the application, business logic code :)
🚀
