Elementi taggati con: jsxc
After more than 7 months of active development, Converse 4 has finally been released.read more...
This release contains lots of highlights, including rewriting the UI to use Bootstrap 4, support for OMEMO Encryption of private messages, message corrections and file-sharing via HTTP file upload.
XMPP is an IETF standardized messaging and presence protocol with multiple independent server and client implementations.
Unlike other popular open source teamchat applications like Mattermost and Rocket.chat, Converse doesn't depend on any particular server (e.g. backend) application. Any XMPP server which supports the relevant extensions (aka XEPs) will do.
#community #xmpp #freesoftware #omemo #im #federation #encryption #converse #jsxc
Converse is an XMPP chat client for the web browser, similar to JSXC.
#xmpp #freesoftware #omemo #im #federation #encryption #converse #jsxc
#161XEP-0363: HTTP File Upload
#194Include entity capabilities in outgoing presence stanzas
#337API call to update a VCard
#421XEP-0308: Last Message Correction
#497XEP-0384: OMEMO encrypted messaging
#968Use nickname from VCard when joining a room
#986Affiliation changes aren't displayed in the chat
#1081Allow for shift-enter to insert newlines
#1091There's now only one CSS file for all view modes.
#1094Show room members who aren't currently online
#1106Support for Roster Versioning
#1137Autocompletion and support for XEP-0372 References, specifically section "3.2 Mentions".
* It's now also possible to edit your VCard via the UI
* Automatically grow/shrink input as text is entered/removed
* MP4 and MP3 files when sent as XEP-0066 Out of Band Data, are now playable directly in chat
* Support for rendering URLs sent according to XEP-0066 Out of Band Data.
* Geo-URIs (e.g. from Conversations) are now replaced by links to openstreetmap (works in reverse also)
* Add a checkbox to indicate whether a trusted device is being used or not.
If the device is not trusted, sessionStorage is used and all user data is deleted from the browser cache upon logout.
If the device is trusted, localStorage is used and user data is cached indefinitely.
* Initial support for XEP-0357 Push Notifications, specifically registering an "App Server".
* Add support for logging in via OAuth (see the oauth_providers setting)
"This is a list of Free Software network services and web applications which can be hosted locally. Selfhosting is the process of locally hosting and managing applications instead of renting from SaaS providers."
There are all kinds of categories, e.g. Search Engines:
- Ambar - Document Search Engine (OCR, Store & Search) (Demo, Source Code) MIT Nodejs/Python
- Gigablast - open source search engine. (Demo, Source Code) Apache-2.0 C++
- Seeks - Web search proxy and collaborative distributed tool for websearch. (Source Code) AGPL-3.0 C++
- Searx - Privacy-respecting, hackable metasearch engine. (Demo, Source Code) AGPL-3.0 Python
- Yacy - Peer based, decentralized search engine server. (Demo, Source Code) GPL-2.0 Java
- Git Annex - File synchronization between computers, servers, external drives. (Source Code) GPL-3.0 Haskell
- Kinto - Kinto is a minimalist JSON storage service with synchronisation and sharing abilities. (Source Code) Apache-2.0 Python
- Nextcloud - Access and share your files, calendars, contacts, mail and more from any device, on your terms. (Demo, Source Code) AGPL-3.0 PHP
OpenSSH/SFTP - Secure File Transfer Program. (Source Code) BSD C
- ownCloud - All-in-one solution for saving, synchronizing, viewing, editing and sharing files, calendars, address books and more. (Source Code, Clients) AGPL-3.0 PHP
- Pydio - Turn any web server into a powerful file management system and an alternative to mainstream cloud storage providers. (Source Code) AGPL-3.0 PHP
- Samba - Samba is the standard Windows interoperability suite of programs for Linux and Unix. It provides secure, stable and fast file and print services for all clients using the SMB/CIFS protocol. GPL-3.0 C
- Seafile - File hosting and sharing solution primary for teams and organizations. (Demo, Source Code) GPL-2.0 C
- SparkleShare - Self hosted, instant, secure file sync. (Source Code) GPL-3.0 C#
- Syncany - Secure file sync software for arbitrary storage backends, an open-source cloud storage and filesharing application. Securely synchronize your files to any kind of storage. GPL-3.0 Java
- Syncthing - Syncthing is an open source peer-to-peer file synchronisation tool. (Source Code) MPL-2.0 Go
- Unison - Unison is a file-synchronization tool for OSX, Unix, and Windows. GPL-3.0 OCaml
- Z-Push - Implementation of Microsoft’s ActiveSync protocol. (Source Code) AGPL-3.0 PHP
- Kaiwa - Web based chat client in the style of common paid alternatives. (Source Code) MIT Nodejs
- Movim - Modern, federated social network based on XMPP, with a fully featured group-chat, subscriptions and microblogging. (Source Code) AGPL-3.0 PHP
- Salut à Toi - Multipurpose, multi frontend, libre and decentralised communication tool. AGPL-3.0 Python
- Libervia - Web frontend from Salut à Toi. (Source Code) AGPL-3.0 Python
Daniel Gultsch, developer of Android XMPP client Conversations, writes,
#xmpp #omemo #conversations #psi #gajim #zom #chatsecure #dino #jsxc #federation #encryption
Why it took us more than two years to enable End-to-End encryption by default: The first in a series of essays leading up to the release of Conversations 2.0
The other big hurdle we had to overcome was the adoption rate in clients. If you send OMEMO encrypted messages by default you should have a reasonable expectation that your contact will be able to decrypt the message. Reasonable expectation doesn’t mean that every single client out there has to support it—In an ecosystem with hundreds of small, badly maintained clients that’s just not feasible—but the major clients should at least have a plugin available.
In March 2018 we finally reached the point where every plattform has one or more clients with OMEMO support. Conversations and Zom on Android, ChatSecure on iOS, Psi and Gajim on the desktop. The up and coming desktop client Dino—despite not having had an initial release—already has support for OMEMO as well. And even the webclient JSXC has a plugin available.
Considering the complexity of OMEMO and the fact that most of these clients are developed by people in their spare time, this is actually quite an impressive adoption rate.
Moxie Marlinspike, in his 2016 propaganda piece ignorantly bashing XMPP, had one valid point: Enabling end-to-end encryption in a homogenous environment is easier than introducing it in a heterogenous one like Jabber. Nobody is denying that. However, if something is hard to achieve there are two possible approaches: Either try your best and don’t give up, or put your head in the sand and create yet another walled garden that is no different from other proprietary solutions.
Admittedly it has taken us a while to get to a point where we can enable end-to-end encryption by default, but it was worth the effort in that we ended up with something that is different from WhatsApp in more than just marketing.