OMEMO conversations work in Monal. There is still a lot work to be done here to properly handle keys and make UI elements in OSX and iOS for all the the new interactions. There is a lot that also needs to be tested before this is in ready for the App Store. Realistically, expect to start seeing this stuff in the binaries I release some point in August.
I have tested this with gajim on linux and chat secure on iOS. Will have dust off an android device somewhere to try it with Conversations.
I have released 3.0.2 to the iOS App Store. So far I appear to have resolved the worst crashes.
I have an update on the status of OMEMO in Monal. I’ve completed my spike and have a very rough implementation working. I am able to communicate with Gajim and Chatsecure. I am actually using a lot of the same OMEMO code as Chatsecure using Chris’ cocoapods. The shared code base should reduce duplicated effort and ensure compatibility on the two main Apple platform clients going forward.
The current code isn’t anywhere near production but once I clean it up more, you should start seeing it as an option to turn on in Mac betas in the next month or so. Below you can see my interactions with Gajim and Chatsecure.
I am still cleaning up all of the issues people have seen (and some old friends) in the latest releases. There are new betas out. I will looking for feedback and crash reports. I hope to have the next updates out this week. I know it has been almost weekly releases since the 3.0 release. Hoping to slow down to a more manageable release cycle after the code is more stable.
The patch release is out. Search is restored and stability should be better.
While I am asking, how has push been in the latest clients? I have seen thousands of devices registered but I haven’t gotten a ton of feedback on how it has worked.
If you don’t have it working yet, you need an XEP-0357 module on your server.
Prosody: Cloud notify
Ejabberd: mod push
Tigase: Push Component
Openfire: Does not support XEP-0357 push notifications
Mongoose IM: mod_event_pusher_push
The first patch update for 2.1 has been released to the App Store. iOS is waiting approval and should be available in a few hours.
There are new Mac and iOS betas out. I am hoping this is the start of these two clients being 100% in sync. This update resolves many of the stability issues in the last release and restores searching to the iOS client.
I appear to have forgotten to add search in the UI on the refactor. It has been re-added and has full iOS 11 and iPhone X support.
As with any big update there are going to be bugs. I know 3.0 is not as stable as the last release. I am working quickly to fix every crash I see. So far the following have been fixed and will be updated next week . It is a long weekend in the US so these will likely come in by Wednesday. Sorry for the problems, know that I am fixing them ASAP. Things fixed so far:
- Crash when trying to save an account with no server has been replaced with an error message.
- Crash on iPads when retrying messages
- Crash on iPads when deleting account
- Crash on fetching message history
- Crash sometimes when receiving messages
- Crash sometimes when logging in
I am looking at the stats coming back and I see one particular crash that I would like to resolve ASAP in both iOS and Mac clients. There will be an update next week after that unless something pressing comes up, development will pause as I sort through GDPR. You may already have noticed the cookie banner that appears on this page courtesy the wp-stats package I am using. The reason for XMPP work stopping: GDPR work is more work and one person only has so much free time in a day.
General GDPR roadmap:
- Site (done)
- Push server