[BUG] Whatsapp service not usable anymore

[matbgn]

Describe the bug

Regarding the official documentation of the Rhymen/go-whatsapp API

Warning
This package is not being actively maintained currently and will soon be unusuable as WhatsApp updates to multi-device. Please look at tulir/whatsmeow for a Go WhatsApp Web API that is actively maintained and supports WhatsApp multi-device.

And the issues opened on it (Rhymen/go-whatsapp#644 & Rhymen/go-whatsapp#651), it seems that this API is no more usable.

Is there a plan to integrate the one proposed (whatsmeow) into Notify in the future?

[nikoksr]

@matbgn thank you very much for the report! And sorry for the inconvenience. I definitely want to keep the WhatsApp service alive, so I or someone else will take care of it as soon as possible.

[slowmanchan]

I can take a crack at it.

[slowmanchan]

Seems like a DB needs to be hooked up for the new package. A default sqlite implementation is provided. Do we want to go this route or keep lookin?

[matbgn]

This is just my personnal opinion, but IF there could be a solution (i.e. with a reasonable amount of research) to avoid an additional SQL DB (even a lite one), I will be more than glad.

[nikoksr]

@slowmanchan appreciate your efforts and sorry for the late response. This one just kinda got lost in the wild for me.

Just in case that you're still interested in implementing this, I'd prefer the WhatsApp service to have a "bring it yourself" solution for the storage. Meaning, the service should expose a way for the user to set and provide their own storage solution via an interface or object. An additional default and minimalistic in-memory solution would be okay with me, too!

Let me know what you think and if you need any help with this. Sorry again for letting you wait for that long.

[matbgn]

Hi there!

Any news @slowmanchan?

Il the mean time it seems that there is a new up-to-date library for WhatsApp written in Go:

https://github.com/tulir/whatsmeow

Any of you want to take a look?