Penambahan Enggine "whatsmeow" untuk Docker Run

[mdestafadilah]

Pak Izin, menarik sekali project sampingan ini. Gimana kalo ditambahkan enggine lain whatsmeow sepertinya menarik juga.

[rmyndharis]

Hi @mdestafadilah, thanks for the suggestion.

For context on how engines plug in today: OpenWA never calls a WhatsApp library directly. Every session owns one engine object implementing the IWhatsAppEngine TypeScript interface, and the two current engines, whatsapp-web.js and Baileys, are Node libraries loaded in-process behind it.

That is the catch with whatsmeow: it is a Go library, so it cannot be an in-process adapter the way the current two are. Wiring it in would mean a sidecar service in Go plus a new adapter speaking some transport to it, which is a much larger and riskier surface than the existing adapters.

There is no whatsmeow work on the roadmap right now. The direction stays as described in #447: the API layer is engine-agnostic and new engines are not ruled out, but each one has to justify its maintenance cost against what Baileys and whatsapp-web.js already cover.

If you or anyone else want to prototype a whatsmeow sidecar with an adapter that satisfies the interface, that is the kind of contribution we would genuinely look at.

[mdestafadilah]

Sepertinya ada project yang menggunakan enggine go via nodejs

https://github.com/nicastelo/whatsmeow-node

apakah relate pak?