Bug#1026430: profanity: If an OMEMO msg to 2+ recipients & 1 recipient’s pubkey is bad, the msg is sent anyway (a logistical mess)

Package: profanity Version: 0.13.1-1~bpo11+1 Severity: normal X-Debbugs-Cc: debbug.profan...@sideload.33mail.com If a message is sent in a chat room with multiple recipients, and Profanity fails to get a handle on the public key for one of the recipients, Profanity simply neglects to use the key i

Bug#1024899: profanity: some Profanity → Beagle OMEMO msgs give “This message cannot be decrypted for any recipient.”

Package: profanity Version: 0.13.1-1~bpo11+1 Severity: important X-Debbugs-Cc: debbug.profan...@sideload.33mail.com Configuration: Bob has 2 clients → linux:Profanity & Android:Snikket Alice has 2 clients → macos:Beagle & iOS:Snikket server → snikket.org Bob’s Profanity and

Bug#1017049: profanity: No acknowledgement when running “/omemo start” in a chat room; also no docs on this

Package: profanity Version: 0.10.0-1 Severity: normal Tags: upstream X-Debbugs-Cc: debbug.profan...@sideload.33mail.com To send encrypted messages to a chat room, the following steps are necessary: 1) OMEMO must be switched on for that room (enter “/omemo start” within that room) 2) the fing