Chris Ballinger

~Actually hold off on merging this, I'm seeing some test failures: https://github.com/ChatSecure/ChatSecure-iOS/issues/1075~ edit: test failures are because of an unrelated regression. see #14

Is this something that should be revisited soon?

I reached out to a few people and received confirmation that they're aware of the issue and working on it.

@N-Pex Ah good catch. I'm not sure the original reasoning. We do manually add the receipt request: ```swift @objc public func sendRoomMessage(_ message: OTRXMPPRoomMessage) { let elementId = message.xmppId ??...

I think either approach is fine. If you put a PR for XMPPFramework I'd suggest adding a BOOL option that retains the old behavior by default. The sending was decoupled...

I think it's because technically, from the perspective of the room, there are two different occupants that just happen to share a JID. In "anonymous" rooms the occupants real JID...

That option still exists upstream so that must be a bug introduced in Zom. However... I think this option should be removed entirely in favor of system language preferences. It...

iOS apps use something called ATS or "App Transport Security", which blocks all non-https links from loading. This is to prevent things like lazy developers of your banking app accidentally...

I am guessing this is possibly a server capacity issue. The mod_http_upload module wasn't designed for high traffic and should be moved to [mod_http_upload_external](https://modules.prosody.im/mod_http_upload_external.html) with the backend component on another...

That said, we should still implement a 3x auto-retry, but it may introduce additional load onto the server if it is already incapable of handling the requests .