monal-im.org :xmpp:

Open source XMPP client for iOS and macOS with focus on privacy and convenient chatting.

Join our support channel: xmpp:[email protected]?join

MATRIX - 𝐌onolithic, 𝐀wfully 𝐓rendy 𝐑e-𝐈mplementation of 𝐗MPP

iOS: https://apps.apple.com/app/id317711500
macOS: https://apps.apple.com/app/id1637078500
Web: https://monal-im.org/
Source: https://github.com/monal-im/Monal

Public Key

npub1xxsakz442dmz57rx5s4tazelfqenfheha4k3j5v0njxf7fkhfwhqntxwre

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsrrgwmp264xa320pn2g2473vl5sve5mum76mge2x8eerylymt5htspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dskug9d7

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1xxsakz442dmz57rx5s4tazelfqenfheha4k3j5v0njxf7fkhfwhqntxwre

Show more details

Last Notes

2026-07-14 05:58:11 UTC

- reply

yes, that is possible and we can even ship updates even though it won't be accessible in the appstore for new installs (in that case it would need a new SMS code which won't work anymore anyways).

2026-07-14 02:48:46 UTC

- reply

To bring some perspective into this: according to the appstore statistics, Quickly iOS has about 600 users currently (and only 1.8k downloads ever, including later uninstalls).
That's almost nothing compared to the >50k users of Monal iOS.
While there are a hand full of solutions (local users donating a Sim with SMS flat + cheap android device to route through SMS for their country for example), I fully understand @npub18ds…6490 here: according to the user count it doesn't seem worth the effort.

2026-07-13 19:23:58 UTC

We will remove Quicksy from the Appstore shortly. See this for the reason: https://gultsch.social/@daniel/116912137403650656

2026-06-27 08:18:19 UTC

- reply

setting up a [@snikket_im](https://fosstodon.org/@snikket_im ) server is dead easy.
But as an #xmpp client developer I might obviously be biased.
On the other hand I'm a happy xmpp user since 2015 and only later in 2020 joined the Monal team.

2026-05-29 21:21:00 UTC

- reply

while money always helps to attend xmpp sprints and pay our push server infrastructure, what we need most is more contributors. There is so much left to do for Monal 7.0, every helping hand would be awesome! :)

2026-05-29 18:16:49 UTC

- reply

we are working on stickes in Monal 7.0, we even have our own stickerpacks created by @npub1nw5…zvpk already :)

2026-04-14 02:00:20 UTC

- reply

Every time I read this, a question pops up in my mind: what would "a consistent ui" be like? I means: iOS and android, for example, sometimes have vastly different ui concepts and using the android concepts on iOS would feel very weird to the users, no?

2026-03-29 21:03:55 UTC

- reply

like @npub1y49…j8wa already said, I don't think that this is necessarily true.
But on top of this: matrix/element got a *lot* more money pumped into reinventing the wheel. If all that money reached xmpp instead, I'm almost sure we now would have something superior to current matrix and current xmpp alike at our hands.

2026-03-29 20:51:41 UTC

- reply

regarding the attack vector, Holger die a nice writeup on what this actually is over here: https://metalhead.club/@holger/116239792302016942

2026-03-15 19:43:05 UTC

- reply

beware though, that dialback has weaker security properties than proper can certificate validation. So of should only be enabled as interim solution.

2026-03-15 13:12:34 UTC

- reply

oh and regarding snikket/siskin: I didn't check that again, but I thought even those try to use normal silent pushes delivered to the main app for non-body xep-0357 pushes to keep things up to date and only send app extension reaching high priority pushes when receiving 0357 body-pushes.
But yes, I might be mistaken here, sorry.

2026-03-15 13:07:38 UTC

- reply

Given that the current mod_csi_simple, places the queue *after* smacks and solving that either involves major refactoring of csi_simple and/or smacks and push modules, I figured it would take much time to do that and won't be something fixed in the next couple of weeks (especially given the fact that you might rather have more important things to do than fixing csi_simple). So I decided to suggest switching the csi module as solution applicable now. At least until csi_simple was fixed.

2026-03-15 13:04:08 UTC

- reply

sorry, I didn't want to step on anybody's feet, but as far as I understand the relationship has been for years (mod_csi_pump for example): csi queue -> smacks queue -> tcp connection. Which makes sense given that stanzas reaching the hibernated csi queue should trigger a push and you don't want pushes for stanzas marked as not important by csi.
1/2

2026-03-14 19:35:56 UTC

Heads up for all prosody server admins: don't use mod_csi_simple, it is broken and will result in way more pushes and vastly higher battery drain on all iOS devices! (Even when using siskin or snikket instead of Monal)
You can use mod_csi_battery_saver instead, which doesn't have any of these problems.

2026-03-14 19:24:19 UTC

Monal 6.4.19 (Build 1085, PR #1583) released.
To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1085
#Monal #ios #macos #xmpp #im #chat #messaging

2026-03-11 23:31:07 UTC

- reply

my attitude is that I expect maintainers to maintain things, just like I'm maintaining my project fixing bugs when they get reported. Especially if those bugs render the app unusable for a huge portion of users (as with this ejabberd bug rendering ejabberd nearly unusable).

2026-03-11 23:08:25 UTC

- reply

okay, I guess I have to publish a post telling my users to switch the server to prosody then, or switch from Debian to nix 🤷‍♂️

2026-03-11 23:05:56 UTC

- reply

aren't you a maintainer of the ejabber packet? I might have misunderstood the term "maintainer", but shouldn't you, uhm, maintain the packet then?
Why should I start maintaining the packet? Do you mean you aren't capable of doing it and want to resign your maintainership of that packet?

2026-03-11 22:58:57 UTC

- reply

didn't you talk about updating Debian? Shouldn't fixing stable be top priority for you?
And no, I'm neither Debian developer nor do I have enough Erlang experience to do that, but *I* will be the person that has to answer all those support requests once our push server certs still having client auth eku expired and push stops working.
And to be clear: on iOS push is vital for a usable client.

2026-03-11 22:51:58 UTC

- reply

and what about fixing stable first?

2026-03-11 22:46:55 UTC

- reply

ah, so youre talking about that p1 TLS module? That wasn't entirely clear to me.

2026-03-11 22:41:18 UTC

- reply

unfortunately there is no package, not even in sid, having the needed commit from Holger over here: https://salsa.debian.org/ejabberd-packaging-team/ejabberd/-/commits/trixie?ref_type=heads
Without that, even an updated p1 TLS packet is useless 🤷‍♂️
Not even starting to talk about Debian stable...

2026-03-11 22:36:41 UTC

- reply

well, its a lot of work to do, but you could help ;)
The current state of the new ui is already visible / somewhat usable in the alpha builds. And in the Monal channel are currently screenshots of the new ui :)

2026-03-11 22:34:09 UTC

- reply

how is it going with the update?
The webpki moving away from client auth eku is slowly breaking all s2s connections with Debian servers running ejabberd.

2026-03-11 20:19:04 UTC

- reply

no I can't. I'm already investing *way* too much time into Monal and am already neglecting important other parts of my live and regular job, I won't invest even more time into Monal and there is already a metric ton of bugfixes and features on my to do list.
As I said: I happily take pull requests if somebody is willing to implement things, but I have to make a cutoff somewhere and here it is.

2026-03-11 20:12:57 UTC

- reply

somebody then has to decide which jitsi servers to include as preset in Monal. And of course also implement that feature.

2026-03-11 19:51:16 UTC

- reply

The ban was because Monal allows users to freely express and share their views without the government being able to control what is being said/shared.
I don't believe the government will unban Monal (or quicksy once it got banned, too) if it doesn't implement some sort of spying functionality for them. And I won't ever do that!
I'm afraid there aren't many options left here besides getting rid of the oppressive government 🤷‍♂️

2026-03-11 19:47:57 UTC

- reply

regarding the talking point "alternative for wechat": I believe the Chinese government doesn't want a solution to exist that's not under their control. That's the reason why they banned Monal from the appstore as soon as they deemed it too popular.
And I'm sure they will ban quicksy as well and only did not yet, because its user base is really small.

2026-03-11 19:42:55 UTC

- reply

a solution is to change the locale of your phone to something else than CN/CHN. This will automatically enable the call functionality. But I'm legally not allowed to use callkit in China, hence the "geoblocking" using the locale.
And as I said: implementing a replacement for callkit us not trivial and I simply don't have the time to do it.

2026-03-11 19:39:54 UTC

- reply

quicksy isn't banned from the appstore in China, only Monal is. The problem is, that apps for the Chinese appstore aren't allowed to use callkit, Apple's framework for seamless VoIP calls. This framework is used and deeply integrated in the call management code of Monal. Somebody has to write a replacement for this.
I'm not capable of singlehandedly improve the whole world for everybody, so this must be done by somebody else. There are already a whole lot of tasks in Monal I'm working on.

2026-03-11 16:44:05 UTC

- reply

sorry, no...I do this in my spare time and I can't solve every problem and implement every wish. If that many people are impacted by this, like you say, surely some of these might be able to implement it.
Or overturn the Chinese government with something less oppressive so that the ban for using the built-in iOS call ui can be used in China again 🤷‍♂️

2026-03-11 14:45:19 UTC

- reply

I take pull requests, so if someone is willing to implement an extra ui and "incoming call" interface for China: go ahead and do so :)
https://github.com/monal-im/Monal
Please don't submit ai slop, though. I will ban all users submitting slop.

2026-03-11 14:29:03 UTC

- reply

no idea why China bans the iOS native interface but allows apps to develop their own ui and call screen. I guess they want to raise the bar for independent VoIP apps 🤷‍♂️
But I don't care since the main app (Monal) was banned completely in China, see https://monal-im.org/post/00010-ios-banned/

2026-03-11 14:19:53 UTC

- reply

you cannot call your own account ("notes to self" contact) nor call a group or channel. And calling under macOS isn't implemented (but you are on iOS, right?)
China doesn't allow apps to use the native call interface of iOS, thus calling isn't enabled if your locale is set to CN or CHN.
Calling in Monal is allowed in China btw., because they banned the whole app from the Chinese appstore. So if you manage to install the app, you will be able to use calls even in China now :D

2026-03-11 13:58:48 UTC

- reply

https://cdn.fosstodon.org/media_attachments/files/116/210/894/235/656/195/original/5c8afe863379fbec.jpg

2026-03-11 13:37:14 UTC

- reply

yes, just tap onto the telephone icon in the top right corner of a chat.

2026-03-08 11:05:05 UTC

- reply

I think @npub18ds…6490 once told me that it will ask you to trust the new device before sending a message.

2026-03-08 10:59:09 UTC

- reply

ah and Monal shows a notification if a new client was added to your own account. Usually that's more actionable because somebody (e.g. you server operator) could try to sneak in a new device to be able to decrypt your conversations.
So you shouldn't ignore that, if it wasn't you logging in on a new device. You can ignore it if you never manually trusted one of your own devices and you should trust this new device if you manually trusted at least one of your own devices.

2026-03-08 10:55:24 UTC

- reply

the only thing Monal does differently is: it shows a status message in-chat if the remote end added or removed a new device. I could be convinced to not show these if there is no manual trust (as described above) involved for this contact.

2026-03-08 10:51:21 UTC

- reply

Monal actually does the same as Dino and Conversations: if you never manually trust any device/key, new devices are automatically trusted.
If you manually trusted any key in the past, new devices won't automatically be trusted, because you proved that you want to manually control which devices you trust and which you don't.
If you have a specific scenario in which Monal didn't do exactly this, please share so that I can fix things :)

2026-03-01 19:19:04 UTC

- reply

ich hab das einfach so gemacht: wer mich kontaktieren will braucht entweder eine xmpp app oder muss mir halt eine SMS schreiben. Es ist erstaunlich wie schnell sich dann Leute lieber eine xmpp app zulegen, sobald sie etwas mehr mit mir schreiben :D

2026-02-24 20:20:13 UTC

- reply

thanks! Not sure. I thing the bug was present in both.
See Herr for the logging part: https://github.com/monal-im/Monal/wiki/Introduction-to-Monal-Logging
Please send the log via email to [email protected]

2026-02-24 17:12:01 UTC

- reply

the question is: could you try again, if the false regenerating of your keys still happens and if so maybe provide a logfile?
It should be fixed IMHO, but you never know...

2026-02-24 17:10:32 UTC

- reply

because there is now way to know if the old device was wiped after the migration or if there are now two devices with identical omemo deviceids and keys.
Two devices having the exact same identity will cause encryption/decryption problems. And there are also the security implications of the duplicated keys along with your chat partners not being able to determine if your device was cloned or is still only one single device.

2026-02-24 16:49:59 UTC

- reply

sure, but imho that bug has already been fixed several month ago. It was related to apple not returning a stable ID from an api supposed to do exactly that.
We used that ID to regenerate the keys after device migration.
We now generate and store our own ID in the password storage, to detect if the device was migrated.

2026-02-24 11:23:21 UTC

- reply

you can try Monal, it is available via homebrew and in the macOS appstore :) No audio/video calls on macOS, though, only on iOS.

2026-02-21 16:00:16 UTC

- reply

what about @npub1lv6…5udt ?
https://piaille.fr/@movim/116098387611211972

2026-02-21 15:57:27 UTC

- reply

Im Unterschied zu Signal sind diese Metadaten aber nicht alle zentral bei einem einzigen Anbieter, sondern verteilt und der Anbieter auch wechselbar.

2026-02-21 15:56:42 UTC

- reply

was es deutlich erstrebenswerter als Signal macht ist der föderierte Aufbau. Bei signal ist man immer noch auf Gedeih und Verderb einem einzigen Anbieter ausgeliefert und der ist beispielsweise im Signal Fall abhängig von Amazons AWS Cloud.
Was Metadata angeht, fällt bei #XMPP zwar etwas mehr an, allerdings kann Signal beispielsweise auch Kommunikationspatterns wie "wer mit wem und wann" erschließen.

2026-02-21 15:52:52 UTC

- reply

die Negativliste betrachte ich als ziemlich veraltet...omemo Verschlüsselung ist standardmäßig eingeschaltet und funktioniert auch in Gruppen (muc) wunderbar, nicht nur auf Android sondern auch auf IOS oder in Dino und Gajim als Desktopclients. Aber der Artikel ist ja auch schon 5-6 Jahre alt, da ist das ja nicht verwunderlich.
Und beide Clients sind mit voreingestellten Servern, können also tatsächlich installiert, gestartet und nach 3 mal "weiter" drücken genutzt werden

2026-02-21 09:35:02 UTC

- reply

Ich würde ja xmpp empfehlen.
Das ist quasi der direkte WhatsApp Ersatz, nutze den schon seit >10 Jahren für Freunde und die gesamte Familie.
Gibt super Clients wie Conversations auf Android und Monal auf IOS Geräten.
Disclaimer: wie meinem Account zu entnehmen, arbeite ich mittlerweile seit 2020 an Monal, mein Einstieg zu xmpp und die Umstellung meiner gesamten Kommunikation war aber bereits 2015.

2026-02-12 20:15:06 UTC

- reply

we are currently rewriting the complete chat ui to be able to deliver all these modern features (reactions etc.). Unfortunately this is a big task and will take ~9 month (rough estimate).
Copying a message and more is already possible by swiping the message to the left to get the list of options.

2026-02-12 19:58:07 UTC

- reply

right, exactly that. Normally Conversations and Monal remove devices from the encryption list, if they have not been seen/used for more than 90 days.
This list is used to determine on which devices a message should be decryptable. (You don't want an old maybe even lost device to still receive all your past e2e encrypted messages once turned on by someone).

2026-02-10 15:55:21 UTC

- reply

Snikket for iOS and siskin might both suffer from notification/push issues (notifications doubled, notifications missing), but all messages should always be there if you open the app (if you have internet connectivity when opening the app, otherwise messages you already got notifications for might still not be displayed in the app).
Monal doesn't suffer from all these issues.
The only issue is this (due to iOS restrictions): https://social.tchncs.de/@ludman1/115606583313028390

2026-02-09 11:38:46 UTC

- reply

great, let me know if something doesn't work.
We are currently working on a complete rewrite of the chat ui. This will allow us to implement reactions, rich replies, stickers etc.

2026-02-08 19:09:58 UTC

Monal 6.4.18 (Build 1077, PR #1555) released.
To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1077
#Monal #ios #macos #xmpp #im #chat #messaging

2026-02-08 15:47:19 UTC

- reply

Monal Bad a bug that made audio to Dino as well as Video to Dino and Conversations sometimes not work (~50% of time)
The next stable release that should reach the appstore in a few days will fix that :)

2026-02-07 15:06:16 UTC

- reply

yes, Monal we changed a lot. Since 2020 we gradually replaced every part of the app with completely new code. In Monal 5.0 a completely new group/channel implementation was introduced and in 6.0 audio and video calls were added.
Currently we are half part through rewriting the complete ui using Apple's new SwiftUI framework.
You can find the changelog here: https://github.com/monal-im/Monal/releases?page=1
When did you try Monal the last time?

2026-02-07 00:27:38 UTC

- reply

did you try Monal? It should have everything you need.

2026-02-01 23:25:48 UTC

- reply

don't ever use chatsecure, that project has been abandoned for several years now, I don't even know if it works properly with modern Xmpp.
If you want proper push support you should use Monal instead of Siskin or Snikket for iOS. The latter ones made a design decision that works badly with Apple's push design.
For No all you won't even need the extra snikket push modules for prosody and Monal properly works on ejabberd, too.

2026-02-01 13:56:22 UTC

- reply

The author heavily relies on AI to get things done.

2026-02-01 13:54:31 UTC

- reply

I personally wouldn't trust an app that is written mostly by AI and still tells you it is the "most secure" one.

2026-01-31 16:26:47 UTC

- reply

The videocall bug has been fixed in the latest release, but it introduced another bug in an upstream library that broke video calls completely, but only in one call direction.
The fix for this second bug is already released as beta (testflight) but not yet as stable (expect it to be released in the next couple of days).

2026-01-30 11:42:30 UTC

- reply

yes it is unfortunately.

2026-01-30 09:19:20 UTC

- reply

using Thunderbird as xmpp client is like using Netscape navigator from 1990s to browse the modern web: it just won't work out.
I personally hate the fact that Thunderbird has "xmpp" included. It contributes significantly to the impression xmpp wasn't usable.
Regarding the omemo message: all modern clients moved to end to end encryption for better privacy, Thunderbird just did not make that move, too, so it isn't able to decrypt incoming messages.

2026-01-29 16:46:49 UTC

- reply

Don't worry, I don't use that platform as my daily driver either, I only happen to write a client for it :D thanks for your kind words btw :)
As for twomemo, the problem has been the lack of a usable library and now it is the lack of time (at least for me). Rewriting the chat ui consumes almost all time available for Monal.

2026-01-29 15:16:36 UTC

- reply

what client and which encryption scheme?

2026-01-19 13:37:18 UTC

- reply

once you archive a chat you just have to open it again through your contactlist to see the messages again.
While XMPP *is* cross platform (we have apps for all major platforms, only a single branding name was missing, but that is solved by Snikket now), the less polished appearance mainly comes from lack of resources (developers/money) not from the protocol itself.
Moving to Signal won't fix this but rather make this problem more severe.
Btw: most clients support OMEMO encryption.

2026-01-19 13:03:19 UTC

- reply

could you tell me what part of #Monal is low quality? I'd be more than happy to improve things!

2026-01-07 07:44:37 UTC

- reply

one step at a time would mean to implement mam, carbons, xep-0198, xep-0333, xep-0184 before implementing onemo. And then probably also implement sasl2 (xep-0388) + ssdp (xep-0474).

2026-01-05 23:57:17 UTC

Monal 6.4.17 (Build 1072, PR #1541) released.
- Removed christmas special again
- Added Estonian and Telugu translations
- Fixed random black video feed on video calls
- Make it harder for spammers to mention everybody: ignore mentions if more than 5 participants are mentioned per message
- Properly display Visitor role in Channels
- Add "Request Voice" button to contact details of moderated Channels
#Monal #ios #macos #xmpp #im #chat #messaging

2025-12-29 19:22:21 UTC

- reply

push tokens are the link between your signal account on one side and google/apple account on the other. If you know the google/apple account you can ask google/apple for the token and then signal to block all accounts using that token.

2025-12-23 23:50:15 UTC

Monal 6.4.16 (Build 1069, PR #1526) released.
- Fixed Add Account screen
#Monal #ios #macos #xmpp #im #chat #messaging

2025-12-23 19:45:14 UTC

Monal 6.4.15 (Build 1067, PR #1521) released.
To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1067
#Monal #ios #macos #xmpp #im #chat #messaging

2025-12-20 18:41:10 UTC

- reply

monal is looking like shrek doing yoga? How's that?

2025-12-14 14:59:46 UTC

Heads up for all translators: Please make sure to enable notifications for new strings in your weblate settings, to be notified about new untranslated strings for the languages you maintain!
That's especially important for changelog entries as these are "short lived".

2025-12-13 10:56:33 UTC

- reply

I'd be more than happy to merge a pull request fixing that. But so far I only got AI vibe coded bullshit that cost me several hours to review and test :(

2025-12-13 10:55:04 UTC

- reply

thats a known problem I genuinely don't know an answer for. Monal uses libWebRTC just like Conversations and the fact that audio still works even if the video stream fails, leaves me deeply puzzled. I can only guess that this is some race condition, either in libWebRTC on iOS or in the way/timing/order Monal uses its api.
But unfortunately heisenbugs like this one are really hard to debug. I already spent several hours trying to fix this but to no avail.

2025-12-08 23:56:09 UTC

- reply

ox is well on my ToDo list, once the new chat ui is ready :)

2025-12-06 02:10:50 UTC

Appstore metadata (description etc.) and even the changelog visible in the appstore are now translatable via weblate! 🥳
https://hosted.weblate.org/projects/monal/
Happy translating! 😊

2025-11-28 19:14:14 UTC

- reply

Friedrich and I once did an experiment: we switched off all pushes for his device and solely used the background tasks. He didn't experience much difference. In particular the notifications for messages sent during the night came in shortly after he switched flight mode off in the morning.
But Friedrich was a heavy user, using monal as main communication app for family and friends.
--> your friend probably doesn't use monal frequently enough compared to these other apps. /2

2025-11-28 19:10:22 UTC

- reply

my only guess would be that these apps send out periodic pushes, maybe once per hour. How much time does pass between going online and notifications coming in?
My second guess: the periodic background time an app is allowed to get depends heavily on its usage. So if an app is used much its granted more background time. And iOS tries to determine when an app normally will be used and start the background task around that time. /1

2025-11-27 13:51:08 UTC

- reply

not sure. For monal we try to schedule periodic background syncs to catch these push-swallowed cases. But that only works if you don't force close the app (eg not swipe it away and don't restart your phone).

2025-11-27 13:22:23 UTC

- reply

btw you should check the considerations for server admins over here: https://github.com/monal-im/Monal/wiki/Considerations-for-XMPP-server-admins

2025-11-27 13:17:54 UTC

- reply

that's an apple restriction: pushes to offline devices aren't reliable and nearly always get lost. Writing a second message to trigger another push, once the iPhone is online again, will always wake up monal and allow it to retrieve both waiting messages.
Side note: in siskin/snikket iOS, the notification for the first message will be lost and you won't get a notification for it even if you get a notification for the second one. Monal is different (see above).

2025-11-22 11:44:55 UTC

- reply

webxdc is also on my todo list for Monal :)

2025-11-20 04:47:54 UTC

- reply

me too 😁

2025-11-20 04:45:06 UTC

- reply

da war Martin jetzt einfach ein paar Stunden schneller als ich mit dem Link.
Auch interessant ist diese "Begegnung", die ich mit whatsapp vor ca. 1 1/2 Jahren als Monal Maintainer hatte: https://fosstodon.org/@Monal/115580154408122598

2025-11-13 18:05:48 UTC

Monal 6.4.14 (Build 1053, PR #1459) released.
To see the complete list of bugfixes and improvements, check our releases page: https://github.com/monal-im/Monal/releases/tag/Build_iOS_1053
#Monal #ios #macos #xmpp #im #chat #messaging

2025-11-03 21:22:24 UTC

- reply

nice! Monal does this, too. Its off by default, but maybe I should turn it on by default.

2025-11-01 00:13:58 UTC

- reply

the Monal Logo is outdated. And heads up: we will have another iteration of the logo when monal 7.0 arrives.

2025-10-21 21:41:45 UTC

- reply

I frequently get questions why the history can't be fetched from the server again. So I'd even argue that OX would be enough for most users. It provides encryption without that forward secrecy hassle most users don't need anyway.
If someone manages to steal your E2E key from your device, they would be able to steal your unencrypted chat history from that device, too. That doesn't change if you use a e2e forward secrecy scheme.
Journalists and activists are a different story of course.

2025-10-21 21:32:52 UTC

- reply

yes, but in my opinion the possibility of turning off omemo in clients is a feature, not a bug.
I want to be able to store my chat history on my own server and fetch it with whatever client I like to use. Forward secrecy breaks that.
And I don't even need e2e encryption if I trust my own self-managed server! (That said, if OX gets implemented by major clients, I might switch to OX. It won't provide forward secrecy, but as argued above, I don't need that at all.)

2025-10-21 12:49:11 UTC

- reply

#omemo, the encryption used in #xmpp is using the same double-ratchet encryption like Signal. In fact many projects even use libsignal internally.

2025-10-20 12:41:08 UTC

- reply

einfach per mail an [email protected] schicken :)

2025-10-20 12:40:42 UTC

- reply

danke, das wäre sehr nett! :)

2025-10-20 12:37:50 UTC

- reply

wenn es immer noch nicht geht, hätte ich sehr gerne eine logdatei, damit ich das debuggen kann. So sollte es nämlich definitiv nicht sein!
Vielleicht bist du auch nicht der einzige, der den bug hat und es ist halt nur noch nie bis zu mir vorgedrungen...
https://github.com/monal-im/Monal/wiki/Introduction-to-Monal-Logging

2025-10-19 18:36:02 UTC

- reply

Was helfen kann sind SRV records für direct TLS, und ein höheres smacks tineout.
Siehe https://github.com/monal-im/Monal/wiki/Considerations-for-XMPP-server-admins

2025-10-19 18:34:39 UTC

- reply

Außerdem versucht Monal bei einem eingehenden Push, für den er den Server nicht kontaktieren kann, extra Background Time von IOS zu beantragen. Die bekommt er dann in der Regel ca. 20 Minuten später (wenn es noch nicht "zu oft" am Tag passiert ist). Diese extra Zeit bekommt Monal aber leider nur, wenn man die App nicht weg gewischt hat.

2025-10-19 18:32:27 UTC

- reply

Wenn später noch ein Push ankommt, dann holt Monal beide wartenden Nachrichten ab. Allerdings ist das natürlich bei einem Account mit nur sehr wenigen Kontakten und keinen (hoch frequentierten) Gruppen/Channels hinreichend selten, dass es sich in so einem Fall nicht unbemerkt selbst heilen kann.
(2/2)