Conversation

Notices

1. Embed this notice
   Etienne (etienne@diaspodon.fr)'s status on Sunday, 19-Jan-2025 22:48:57 JST Etienne

   • Matthew Fennell

   @matthew Hello! I'm setting up internal messaging for a community of about 55 people and going the #Snikket route.

   I started testing the app with a few people, but using ConverseJS is a bit confusing: upon joining an existing chat I keep seeing the following message in existing threads:

   "I sent you an OMEMO encrypted message but your client doesn’t seem to support that."

   Is it a situation you're familiar with, by any chance?

   • Embed this notice
     Matthew Fennell (matthew@social.fennell.dev)'s status on Sunday, 19-Jan-2025 22:48:55 JST Matthew Fennell

     in reply to

     @etienne hello! I'm not an expert, but one thing to check:

     Does this problem happen only for existing messages, or also for new messages sent while Converse is running?

     Reason I ask: when a message is encrypted with OMEMO, it is only encrypted for the devices that already exist.

     This has some nice security benefits but also means when you set up a new client, it can't decrypt the old messages.

     It "should work" with new messages - so if it doesn't, that suggests an incompatibility or bug 🙂

   • Embed this notice
     Matthew Fennell (matthew@social.fennell.dev)'s status on Monday, 20-Jan-2025 04:15:20 JST Matthew Fennell

     in reply to

     @etienne agreed, this kind of thing has caused some confusion among my non-technical friends as well.

     Good luck - I hope you can make it fit what you need!

   • Embed this notice
     Etienne (etienne@diaspodon.fr)'s status on Monday, 20-Jan-2025 04:15:21 JST Etienne

     in reply to

     • Matthew Fennell

     @matthew That makes sense, thanks for your reply.

     This is not a very user-friendly message to be honest. If I'm providing an internal chat for a community with lots of non-techy people, I would prefer they would read something like: "Your device don't have access to past messages" or something similar.

     Maybe there's a way to override this message directly in a Converse JS file? I'll try to see what can be done.