You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
It appears without me manually writing any messages.
The complete logfile also seems to contain the raw keys, so for obvious reasons I won't post that anywhere without at least redacting it first. I'll try to remember to do that, the next time I try Profanity+OMEMO.
Also, what Conversations does is to just send the message encrypted, if encryption is enabled, disregarding any devices (I assume you mean XMPP resources?) that do not support encryption.
Also, what Conversations does is to just send the message encrypted, if encryption is enabled, disregarding any devices (I assume you mean XMPP resources?) that do not support encryption.
This is something that needs to be developed, but isn't that easy with the profanity plugin API, but it is on the roadmap.
I see a lot of 'Last message was sent unencrypted.' messages in the chatlog. I assume they correspond to typing notifications or status changes.
The text was updated successfully, but these errors were encountered: