ChatSecure is a free and open source encrypted chat client for iOS that supports OTR and OMEMO encryption over XMPP.
-
Updated
Apr 15, 2022 - Objective-C
{{ message }}
ChatSecure is a free and open source encrypted chat client for iOS that supports OTR and OMEMO encryption over XMPP.
The | state-of-the-art | secure-by-default | one-touch-deployed | XMPP server for everyone.
A WIP secure XMPP client for UWP (Windows 10) devices.
Gajim plugin for OMEMO Multi-End Message and Object Encryption
Officially supported Psi plugins
Tracking the Progress of OMEMO Integration in various clients
Codebase snapshots for Psi+ project
(M) Android XMPP Client
Desktop Jabber/XMPP client based on Converse.js and Electron
A modular and portable open source XMPP client library written in Java for Android and Java (SE) VMs
This should use an abstraction layer over the native implementation. e.g.
Cordova may be supported (https://github.com/blocshop/sockets-for-cordova) but also Node (for Electron)
This issue is not a issue of this repo, it is a general issue with torification.
I always read HowToTorify from TPO wiki but always made an excuse to continue comfortable with my plain debian setup using application proxy settings and torsocks app.
But after spending a lot of time thinking about it, it does not protect you at all if the application developers screw with proxy settings or do
Command Line OMEMO Chat Client - ARCHIVED! Migrated to https://git.jabberhead.tk/vanitasvitae/clocc
OMEMO Instant Messenger is an open source, user-friendly IM client for the Android platform
Downloader for OMEMO-encrypted XMPP files
An experimental implementation of XEP-0384 aka OMEMO for sleekxmpp
Arch Linux PKGBUILD contributions
Add a description, image, and links to the omemo topic page so that developers can more easily learn about it.
To associate your repository with the omemo topic, visit your repo's landing page and select "manage topics."
Describe the bug
When a form, sent via an adhoc command, contains a field named "username", it is not displayed at all.
Expected behavior
username is a valid field name, so the form should be displayed
Environment:
Additional context
I commented a minimal example here: https://github.com/conversejs/converse.js