Conversations: the very last word in instant messaging
This is a fork of the official Conversations app with some modifications described under features.
Conversations can be downloaded from github releases
- Be as beautiful and easy to use as possible without sacrificing security or privacy
- Rely on existing, well established protocols (XMPP)
- Do not require a Google Account or specifically Google Cloud Messaging (GCM)
- Require as few permissions as possible
- End-to-end encryption with either OTR or OpenPGP
- Send and receive images as well as other kind of files
- Share your location via an external plug-in
- Indication when your contact has read your message
- Intuitive UI that follows Android Design guidelines
- Pictures / Avatars for your Contacts
- Syncs with desktop client
- Conferences (with support for bookmarks)
- Address book integration
- Multiple accounts / unified inbox
- Very low impact on battery life
our individual changes:
- accounts are hard linked to pix-art.de
- increased avatar-sizes in account- and contact-details with prefering XMPP-avatars over addressbook avatars
- in-app self updater with dayly check for updates
- moved writing info from chatwindow into actionbar-subtitle
- show lastseen info in actionbar-subtitle
- display group chat members in actionbar-subtitle
- images are transfered as JPEG
- support more file-types for file-transfer (pdf, doc, docx, txt, m4a, m4b, mp3, mp2, wav, aac, aif, aiff, aifc, mid, midi, 3gpp, avi, mp4, mpeg, mpg, mpe, mov, 3gp, apk, vcf, ics, zip, rar)
- show contacts name in locations shared in conferences
- OpenPGP end-to-end encryption methode is disabled
This Conversations works only with pix-art.de. However XMPP is an
extensible protocol. These extensions are standardized as well in so called
XEP's. Conversations supports a couple of these to make the overall user
experience better. Our XMPP-Server is prosody and supports all of the listed XEP's:
- XEP-0065: SOCKS5 Bytestreams (or mod_proxy65). Will be used to transfer files if both parties are behind a firewall (NAT).
- XEP-0163: Personal Eventing Protocol for avatars
- XEP-0191: Blocking command lets you blacklist spammers or block contacts without removing them from your roster.
- XEP-0198: Stream Management allows XMPP to survive small network outages and changes of the underlying TCP connection.
- XEP-0280: Message Carbons which automatically syncs the messages you send to your desktop client and thus allows you to switch seamlessly from your mobile client to your desktop client and back within one conversation.
- XEP-0237: Roster Versioning mainly to save bandwidth on poor mobile connections
- XEP-0313: Message Archive Management synchronize message history with the server. Catch up with messages that were sent while Conversations was offline.
- XEP-0352: Client State Indication lets the server know whether or not Conversations is in the background. Allows the server to save bandwidth by withholding unimportant packages.
- XEP-0363: HTTP File Upload allows you to share files in conferences and with offline contacts. Requires an additional component on your server.
(In order of appearance)
- Rene Treffer (PRs)
- Andreas Straub (PRs)
- Alethea Butler (PRs)
- M. Dietrich (PRs)
- betheg (PRs)
- Sam Whited (PRs)
- BrianBlade (PRs)
- Ilia Rostovtsev (Progress)
- Diego Turtulici (Original)
- fiaxh (OMEMO)
Translations are managed on Transifex for original features
Translations for our own features are managed on github. If you would like to help translation the app create a pull-request.
Conversations is entirely open source and licensed under GPLv3. So if you are a software developer you can check out the sources from GitHub and use ant to build your apk file.
Our modified version of Conversation can be downloaded from github releases
With our Conversations app you can only create and use accounts on pix-art.de. You can create your own account for free. You only need a nickname and a password. You don't need to add @pix-art.de to your nickname. After creating your own pix-art.de account you'll find me in your contact list. If you have any questions about our app or our service feel free to ask me or join our support-conference [email protected].
The address book integration was designed to protect your privacy. Conversations neither uploads contacts from your address book to your server nor fills your address book with unnecessary contacts from your online roster. If you manually add a Jabber ID to your phones address book Conversations will use the name and the profile picture of this contact. To make the process of adding Jabber IDs to your address book easier you can click on the profile picture in the contact details within Conversations. This will start an "add to address book" intent with the JID as the payload. This doesn't require Conversations to have write permissions on your address book but also doesn't require you to copy/paste a JID from one app to another.
If you get delivery failed on images it's probably because the recipient lost network connectivity during reception. In that case you can try it again at a later time.
For text messages the answer to your question is a little bit more complex. When you see 'delivery failed' on text messages, it is always something that is being reported by the server. The most common reason for this is that the recipient failed to resume a connection. When a client loses connectivity for a short time the client usually has a five minute window to pick up that connection again. When the client fails to do so because the network connectivity is out for longer than that all messages sent to that client will be returned to the sender resulting in a delivery failed.
Other less common reasons are that the message you sent didn't meet some criteria enforced by the server (too large, too many). Another reason could be that the recipient is offline and the server doesn't provide offline storage.
Usually you are able to distinguish between these two groups in the fact that the first one happens always after some time and the second one happens almost instantly.
Statuses are a horrible metric. Setting them manually to a proper value rarely works because users are either lazy or just forget about them. Setting them automatically does not provide quality results either. Keyboard or mouse activity as indicator for example fails when the user is just looking at something (reading an article, watching a movie). Furthermore automatic setting of status always implies an impact on your privacy (are you sure you want everybody in your contact list to know that you have been using your computer at 4am‽).
In the past status has been used to judge the likelihood of whether or not your messages are being read. This is no longer necessary. With Chat Markers (XEP-0333, supported by Conversations since 0.4) we have the ability to know whether or not your messages are being read. Similar things can be said for priorities. In the past priorities have been used (by servers, not by clients!) to route your messages to one specific client. With carbon messages (XEP-0280, supported by Conversations since 0.1) this is no longer necessary. Using priorities to route OTR messages isn't practical either because they are not changeable on the fly. Metrics like last active client (the client which sent the last message) are much better.
Unfortunately these modern replacements for legacy XMPP features are not widely adopted. However Conversations should be an instant messenger for the future and instead of making Conversations compatible with the past we should work on implementing new, improved technologies and getting them into other XMPP clients as well.
Making these status and priority optional isn't a solution either because Conversations is trying to get rid of old behaviours and set an example for other clients.
You can choose between different end-to-end encryption methodes, which are explained in the following lines. Our Server only accepts TLS encrypted connections to clients and only allows unencrypted connections to other server, if there is no way to encrypt the connections. If you are chatting with users to other servers, you should use an end-to-end encryption methode or ask me to look if the server-connections are encrypted or not.
In most cases OTR should be the encryption method of choice. It works out of the box with most contacts as long as they are online. However, openPGP can, in some cases, (message carbons to multiple clients) be more flexible. Unlike OTR, OMEMO works even when a contact is offline, and works with multiple devices. It also allows asynchronous file-transfer when the server has HTTP File Upload. However, OMEMO is not as widely supported as OTR and is currently implemented only by Conversations. OMEMO should be preffered over OTR for contacts who use Conversations.
Before you continue reading you should note that the OpenPGP support in Conversations is experimental. This is not because it will make the app unstable but because the fundamental concepts of PGP aren't ready for widespread use. The way PGP works is that you trust Key IDs instead of JID's or email addresses. So in theory your contact list should consist of Public-Key-IDs instead of JID's. But of course no email or XMPP client out there implements these concepts. Plus PGP in the context of instant messaging has a couple of downsides: It is vulnerable to replay attacks, it is rather verbose, and decrypting and encrypting takes longer than OTR. It is however asynchronous and works well with message carbons.
In our version, OpenPGP is diabled because of the problems listed above.
To use OpenPGP you have to install the open source app OpenKeychain and then long press on the account in manage accounts and choose renew PGP announcement from the contextual menu.
For conferences the only supported encryption method is OpenPGP (OTR does not work with multiple participants). Every participant has to announce their OpenPGP key (see answer above). If you would like to send encrypted messages to a conference you have to make sure that you have every participant's public key in your OpenKeychain. Right now there is no check in Conversations to ensure that. You have to take care of that yourself. Go to the conference details and touch every key id (The hexadecimal number below a contact). This will send you to OpenKeychain which will assist you on adding the key. This works best in very small conferences with contacts you are already using OpenPGP with. This feature is regarded experimental. Conversations is the only client that uses XEP-0027 with conferences. (The XEP neither specifically allows nor disallows this.)
If you have troubles or problems please report them first into our support chat [email protected], so we can decide if it's an issue caused by our features or a global issue.
Only global issues should be reported into the Conversations issue tracker. If your app crashes please provide a stack trace. If you are experiencing misbehaviour please provide detailed steps to reproduce. Always mention whether you are running the latest Play Store version or the current HEAD. If you are having problems connecting to your XMPP server your file transfer doesn’t work as expected please always include a logcat debug output with your issue (see above).