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
Create conference rooms with the correct settings (private room, JID exposed). All contacts also need to be manually subscribed to each other.. how to expose in UI?
Fix fingerprint display for contacts (use array of buddies)
MUC entry/exit point for OMEMOModule decryption/encryption
Fetch deviceList / bundles / create sessions for all participants. Make sure it works when a new participant joins, re-showing fingerprint display.
Great work on MUC in the latest code and TestFlight release! Clearly much improved! Thank you for all your hard work!
In looking at our server, it appears that group messages are not OMEMO. Just wondering, did something go wrong on our end or is MUC still not ready for OMEMO?
On Sun, Oct 22, 2017 at 10:24 AM, afriedmanGlacier ***@***.*** > wrote:
Great work on MUC in the latest code and TestFlight release! Clearly much
improved! Thank you for all your hard work!
In looking at our server, it appears that group messages are not OMEMO.
Just wondering, did something go wrong on our end or is MUC still not ready
for OMEMO?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfqHwczOqb6RQVUFts-8dI_sDfeVRrwks5su3o6gaJpZM4KhrL9>
.
@chrisballinger: is in the next release (4.3?) any improvement in the case "GroupChat with OMEMO" to expect? Are there active work about this topic going on at the moment?
Unfortunately this missing feature is a sad fun-stopper in the inter-client-experience with Conversations... :-/
Reacted by contrapunctus-1 and Aminda Suomalainen ⚧
All contacts also need to be manually subscribed to each other..
I think this might not be true (anymore). Conversations has pushed people to enable public access to the OMEMO PubSub node, so it’s not necessarily necessary to have a presence subscription anymore.
Activity
[-]Fix OMEMO group chat[/-][+]OMEMO group chat[/+]afriedmanGlacier commentedon Apr 25, 2017
Any update on when this one might be done (and MUC issues in general)? Still shooting for 4.1?
chrisballinger commentedon Apr 25, 2017
@afriedmanGlacier Please don't use this issue tracker to ask for ETAs unless you have an active support contract.
Thanks!
afriedmanGlacier commentedon Apr 25, 2017
Oops, sorry! I am still not sure of some of the etiquette here
afriedmanGlacier commentedon Oct 22, 2017
Great work on MUC in the latest code and TestFlight release! Clearly much improved! Thank you for all your hard work!
In looking at our server, it appears that group messages are not OMEMO. Just wondering, did something go wrong on our end or is MUC still not ready for OMEMO?
chrisballinger commentedon Oct 22, 2017
mimi89999 commentedon Oct 22, 2017
@chrisballinger I think the milestone should be changed to 4.3
chrisballinger commentedon Oct 22, 2017
Yeah the milestone labels are pretty outdated at this point
therob84 commentedon Jan 25, 2018
@chrisballinger: is in the next release (4.3?) any improvement in the case "GroupChat with OMEMO" to expect? Are there active work about this topic going on at the moment?
Unfortunately this missing feature is a sad fun-stopper in the inter-client-experience with Conversations... :-/
horazont commentedon Apr 6, 2018
I think this might not be true (anymore). Conversations has pushed people to enable public access to the OMEMO PubSub node, so it’s not necessarily necessary to have a presence subscription anymore.