-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OMEMO group chat #580
Comments
Any update on when this one might be done (and MUC issues in general)? Still shooting for 4.1? |
@afriedmanGlacier Please don't use this issue tracker to ask for ETAs unless you have an active support contract. Thanks! |
Oops, sorry! I am still not sure of some of the etiquette here |
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? |
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 I think the milestone should be changed to 4.3 |
Yeah the milestone labels are pretty outdated at this point |
@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... :-/ |
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. |
The text was updated successfully, but these errors were encountered: