<Message is not decryptable on this device>

[namelessperson0]

When a private message is sent though this library, the sender is shown the below message in the inbox from bitclout.com and diamondapp.com
<Message is not decryptable on this device>
The receiver receives the correct message though. But the sender has issues in seeing the message sent.

[ItsAditya-xyz]

hmm, that's weird. I am having that problem as well

likely because the DM is not being encrypted before sending...

[namelessperson0]

Note that receiver is able to read the message without issue. It is only the sender having the issue.

[ItsAditya-xyz]

i think it's an issue with the frontends itself (if the receiver can see the msg, than it's obvious the sender can see it too.
btw, the library doesn't really encrypts the message before sending so i think that might be the issue

[namelessperson0]

But messages sent in frontend do not have this issue.

[ItsAditya-xyz]

yup, because those messages are not encrypted. You can see the payload request while sending a msg

[namelessperson0]

bitclout.com uses "EncryptedMessageText" in post data while this python library uses "MessageText".

In deso-protocol nodejs package, this.identity.encrypt is used to encrypt the message at https://github.com/deso-protocol/deso-workspace/blob/58095ec99eb2010feba55c39e6507bd14d7529b1/libs/deso-protocol/src/lib/social/Social.ts#L44

That encrypt function is defined in https://github.com/deso-protocol/identity/blob/dc744ab49944409b28f36ffe039d39cacf16e92b/src/app/signing.service.ts#L28

I think we will need this package https://github.com/ecies/py for encrypting the message.

[ItsAditya-xyz]

I see. I will try figure that out. Feels free to create a PR to solve this!