Merge pull request 'readme' (#11) from readme into master
Reviewed-on: narayana/conversations-classic#11 Reviewed-by: kosyak <kosyak@narayana.im>
This commit is contained in:
commit
4d52ee060d
79
README.md
79
README.md
|
|
@ -28,11 +28,11 @@
|
|||
|
||||
### XMPP Features
|
||||
|
||||
Conversations works with every XMPP server out there. However XMPP is an
|
||||
Conversations Classic works with every XMPP server out there. 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
|
||||
XEP's. Conversations Classic supports a couple of these to make the overall user
|
||||
experience better. There is a chance that your current XMPP server does not
|
||||
support these extensions; therefore to get the most out of Conversations you
|
||||
support these extensions; therefore to get the most out of Conversations Classic you
|
||||
should consider either switching to an XMPP server that does or — even better —
|
||||
run your own XMPP server for you and your friends. These XEP's are:
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ run your own XMPP server for you and your friends. These XEP's are:
|
|||
client to your desktop client and back within one conversation.
|
||||
* [XEP-0237: Roster Versioning](http://xmpp.org/extensions/xep-0237.html) mainly to save bandwidth on poor mobile connections
|
||||
* [XEP-0313: Message Archive Management](http://xmpp.org/extensions/xep-0313.html) synchronize message history with the
|
||||
server. Catch up with messages that were sent while Conversations was
|
||||
server. Catch up with messages that were sent while Conversations Classic was
|
||||
offline.
|
||||
* [XEP-0308: Last Message Correction](https://xmpp.org/extensions/xep-0308.html) allows you to edit last message as well as retract it
|
||||
* [XEP-0352: Client State Indication](http://xmpp.org/extensions/xep-0352.html) lets the server know whether or not
|
||||
|
|
@ -66,14 +66,10 @@ run your own XMPP server for you and your friends. These XEP's are:
|
|||
|
||||
#### How do I install Conversations?
|
||||
|
||||
Conversations is entirely open source and licensed under GPLv3. So if you are a
|
||||
Conversations Classic 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 Gradle to
|
||||
build your apk file.
|
||||
|
||||
#### I don't have a Google Account but I would still like to make a donation
|
||||
|
||||
I’m listing several options to support me financially on [my website](https://gultsch.de/donate.html). Among other things [Liberapay](https://liberapay.com/iNPUTmice/donate), [GitHub Sponsors](https://github.com/sponsors/inputmice) and bank transfer.
|
||||
|
||||
#### How do I create an account?
|
||||
XMPP, like email, is a federated protocol, which means that there is not one company you can create an *official XMPP account* with. Instead there are hundreds, or even thousands, of providers out there. One of those providers is [conversations.im](https://account.conversations.im). If you don’t like to use *conversations.im* use a web search engine of your choice to find another provider. Or maybe your university has one. Or you can run your own. Or ask a friend to run one. Once you've found one, you can use Conversations to create an account. Just select *register new account* on server within the create account dialog.
|
||||
|
||||
|
|
@ -88,12 +84,12 @@ As of 2023 XMPP has reached a level of maturity where all major XMPP servers ([e
|
|||
Interoperability with Prosody and ejabberd is tested fairly regularly just because of their market share but we occasionally test with other servers too and fix issues as soon as we are being made aware of them.
|
||||
|
||||
#### Where can I set up a custom hostname / port
|
||||
Conversations will automatically look up the SRV records for your domain name
|
||||
Conversations Classic will automatically look up the SRV records for your domain name
|
||||
which can point to any hostname port combination. If your server doesn’t provide
|
||||
those please contact your admin and have them read
|
||||
[this](http://prosody.im/doc/dns#srv_records). If your server operator is unwilling
|
||||
to fix this you can enable advanced server settings in the expert settings of
|
||||
Conversations.
|
||||
Conversations Classic.
|
||||
|
||||
#### I get 'Incompatible Server'
|
||||
|
||||
|
|
@ -104,15 +100,15 @@ If you are a server administrator you should make sure that your server provides
|
|||
either STARTTLS or [XEP-0368: SRV records for XMPP over TLS](https://xmpp.org/extensions/xep-0368.html).
|
||||
|
||||
On rare occasions this error message might also be caused by a server not providing
|
||||
a login (SASL) mechanism that Conversations is able to handle. Conversations supports
|
||||
a login (SASL) mechanism that Conversations Classic is able to handle. Conversations Classic supports
|
||||
SCRAM-SHA1, PLAIN, EXTERNAL (client certs) and DIGEST-MD5.
|
||||
|
||||
#### I get 'Bind failure'. What does that mean?
|
||||
|
||||
Some Bind failures are transient and resolve themselves after a reconnect.
|
||||
|
||||
When trying to connect to OpenFire the bind failure can be a permanent problem when the domain part of the Jabber ID entered in Conversations doesn’t match the domain the OpenFire server feels responsible for. For example OpenFire is configured to use the domain `a.tld` but the Jabber ID entered is `user@b.tld` where `b.tld` also points to the same host. During bind OpenFire tries to reassign the Jabber to `user@a.tld`. Conversations doesn’t like that.
|
||||
This can be fixed by creating a new account in Conversations that uses the Jabber ID `user@a.tld`.
|
||||
When trying to connect to OpenFire the bind failure can be a permanent problem when the domain part of the Jabber ID entered in Conversations Classic doesn’t match the domain the OpenFire server feels responsible for. For example OpenFire is configured to use the domain `a.tld` but the Jabber ID entered is `user@b.tld` where `b.tld` also points to the same host. During bind OpenFire tries to reassign the Jabber to `user@a.tld`. Conversations Classic doesn’t like that.
|
||||
This can be fixed by creating a new account in Conversations Classic that uses the Jabber ID `user@a.tld`.
|
||||
|
||||
Note: This is kind of a weird quirk in OpenFire. Most other servers would just throw a 'Server not responsible for domain' error instead of attempting to reassign the Jabber ID.
|
||||
|
||||
|
|
@ -122,16 +118,10 @@ Maybe you attempted to use the Jabber ID `test@b.tld` because `a.tld` doesn’t
|
|||
|
||||
In most cases this error is caused by ejabberd advertising support for TLSv1.3 but not properly supporting it. This can happen if the OpenSSL version on the server already supports TLSv1.3 but the fast\_tls wrapper library used by ejabberd not (properly) support it. Upgrading fast\_tls and ejabberd or - theoretically - downgrading OpenSSL should fix the issue. A work around is to explicitly disable TLSv1.3 support in the ejabberd configuration. More information can be found on [this issue on the ejabberd issue tracker](https://github.com/processone/ejabberd/issues/2614).
|
||||
|
||||
**The battery consumption and the entire behavior of Conversations Classic will remain the same (as good or as bad as it was before). Why is Google doing this to you? We have no idea.**
|
||||
|
||||
#### I’m getting this annoying permanent notification
|
||||
Starting with Conversations 2.3.6 Conversations releases distributed over the Google Play Store will display a permanent notification if you are running it on Android 8 and above. This is a rule that it is essentially enforced by the Google Play Store. (You won’t have the problem of a *forced* foreground notification if you are getting your app from F-Droid.)
|
||||
|
||||
However you can disable the notification via settings of the operating system. (Not settings in Conversations.)
|
||||
|
||||
**The battery consumption and the entire behavior of Conversations will remain the same (as good or as bad as it was before). Why is Google doing this to you? We have no idea.**
|
||||
|
||||
##### Android <= 7.1 or Conversations from F-Droid (all Android versions)
|
||||
The foreground notification is still controlled over the expert settings within Conversations as it always has been. Whether or not you need to enable it depends on how aggressive the non-standard 'power saving' features are that your phone vendor has built into the operating system.
|
||||
##### Android <= 7.1 or Conversations Classic from F-Droid (all Android versions)
|
||||
The foreground notification is still controlled over the expert settings within Conversations Classic as it always has been. Whether or not you need to enable it depends on how aggressive the non-standard 'power saving' features are that your phone vendor has built into the operating system.
|
||||
|
||||
##### Android 8.x
|
||||
Long press the permanent notification and disable that particular type of notification by moving the slider to the left. This will make the notification disappear but create another notification (this time created by the operating system itself.) that will complain about Conversations (and other apps) using battery. Starting with Android 8.1 you can disable that notification again with the same method described above.
|
||||
|
|
@ -139,39 +129,24 @@ Long press the permanent notification and disable that particular type of notifi
|
|||
##### Android 9.0+
|
||||
Long press the permanent notification and press the info `(i)` button to get into the App info screen. In that screen touch the 'Notification' entry. In the next screen remove the checkbox for the 'Foreground service' entry.
|
||||
|
||||
#### How do XEP-0357: Push Notifications work?
|
||||
You need to be running the Play Store version of Conversations and your server needs to support push notifications.¹ Because *Google’s Firebase Cloud Messaging (FCM)* are tied with an API key to a specific app your server can not initiate the push message directly. Instead your server will send the push notification to the [Conversations App server](https://github.com/iNPUTmice/p2) (operated by us) which then acts as a proxy and initiates the push message for you. The push message sent from our App server through FCM doesn’t contain any personal information. It is just an empty message which will wake up your device and tell Conversations to reconnect to your server. The information sent from your server to our App server depends on the configuration of your server but can be limited to your account name. (In any case the Conversations App server won't redirect any information through FCM even if your server sends this information.)
|
||||
|
||||
In summary Google will never get hold of any personal information besides that *something* happened. (Which doesn’t even have to be a message but can be some automated event as well.) We - as the operator of the App server - will just get hold of your account name (without being able to tie this to your specific device).
|
||||
|
||||
If you don’t want this simply pick a server which does not offer Push Notifications or build Conversations yourself without support for push notifications. (This is available via a gradle build flavor.) Non-play store source of Conversations like the Amazon App store will also offer a version without push notifications. Conversations will just work as before and maintain its own TCP connection in the background.
|
||||
|
||||
You can find a detailed description of how your server, the app server and FCM are interacting with each other in the [README](https://github.com/iNPUTmice/p2/blob/master/README.md) of the Conversations App Server.
|
||||
|
||||
¹ If you use the Play Store version you do **not** need to run your own app server. Your server only needs to support the server side of [XEP-0357: Push Notifications](http://xmpp.org/extensions/xep-0357.html) and [XEP-0198: Stream Management](https://xmpp.org/extensions/xep-0198.html). The prosody server modules are called *mod_cloud_notify* and *mod_smacks*. The ejabberd server modules are called *mod_push* and *mod_stream_mgmt*.
|
||||
|
||||
|
||||
#### But why do I need a permanent notification if I use Google Push?
|
||||
FCM (Google Push) allows an app to wake up from *Doze* which is (as the name suggests) a hibernation feature of the Android operating system that cuts the network connection and also reduces the number of times the app is allowed to wake up (to ping the server for example). The app can ask to be excluded from doze. Non push variants of the app (from F-Droid or if the server doesn’t support it) will do this on first start up. So if you get exemption from *Doze*, or if you get regular push events sent to you, Doze should not pose a threat to Conversatons working properly. But even with *Doze* the app is still open in the background (kept in memory); it is just limited in the actions it can do. Conversations needs to stay in memory to hold certain session state (online status of contacts, join status of group chats, …). However with Android 8 Google changed all of this again and now an App that wants to stay in memory needs to have a foreground service which is visible to the user via the annoying notification. But why does Conversations need to hold that state? XMPP is a statefull protocol that has a lot of per-session information; packets need to be counted, presence information needs to be held, some features like Message Carbons get activated once per session, MAM catch-up happens once, service discovery happens only once; the list goes on. When Conversations was created in early 2014 none of this was a problem because apps were just allowed to stay in memory. Basically every XMPP client out there holds that information in memory because it would be a lot more complicated trying to persist it to disk. An entire rewrite of Conversations in the year 2019 would attempt to do that and would probably succeed however it would require exactly that; a complete rewrite which is not feasible right now. That’s by the way also the reason why it is difficult to write an XMPP client on iOS. Or more broadly put this is also the reason why other protocols are designed as or migrated to stateless protocols (often based on HTTP); take for example the migration of IMAP to [JMAP](https://jmap.io/).
|
||||
|
||||
#### Conversations doesn’t work for me. Where can I get help?
|
||||
|
||||
You can join our conference room on [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im).
|
||||
A lot of people in there are able to answer basic questions about the usage of
|
||||
Conversations or can provide you with tips on running your own XMPP server. If
|
||||
Conversations Classic or can provide you with tips on running your own XMPP server. If
|
||||
you found a bug or your app crashes please read the Developer / Report Bugs
|
||||
section of this document.
|
||||
|
||||
#### How does the address book integration work?
|
||||
|
||||
The address book integration was designed to protect your privacy. Conversations
|
||||
The address book integration was designed to protect your privacy. Conversations Classic
|
||||
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
|
||||
add a Jabber ID to your phones address book Conversations Classic 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
|
||||
details within Conversations Classic. This will start an "add to address book" intent
|
||||
with the JID as the payload. This doesn't require Conversations Classic to have write
|
||||
permissions on your address book but also doesn't require you to copy/paste a
|
||||
JID from one app to another.
|
||||
|
||||
|
|
@ -227,23 +202,23 @@ 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
|
||||
adopted. However Conversations Classic should be an instant messenger for the future and
|
||||
instead of making Conversations Classic 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
|
||||
Conversations Classic is trying to get rid of old behaviours and set an example for
|
||||
other clients.
|
||||
|
||||
|
||||
#### How do I backup / move Conversations to a new device?
|
||||
#### How do I backup / move Conversations Classic to a new device?
|
||||
|
||||
Use the Backup button in the Settings.
|
||||
|
||||
#### Conversations is missing a certain feature
|
||||
#### Conversations Classic is missing a certain feature
|
||||
|
||||
Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im
|
||||
Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im)
|
||||
|
||||
### Security
|
||||
|
||||
|
|
@ -255,7 +230,7 @@ Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`
|
|||
#### How do I use OpenPGP
|
||||
|
||||
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
|
||||
Conversations Classic 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
|
||||
|
|
@ -293,12 +268,12 @@ details and hit the settings button (the one with the gears) and select both *pr
|
|||
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.
|
||||
Right now there is no check in Conversations Classic 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
|
||||
feature is regarded experimental. Conversations Classic is the only client that uses
|
||||
XEP-0027 with conferences. (The XEP neither specifically allows nor disallows
|
||||
this.)
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@
|
|||
|
||||
<resources>
|
||||
<string name="pref_about_message" translatable="false">
|
||||
Conversations • the very last word in instant messaging.
|
||||
Conversations Classic • the very last word in instant messaging.
|
||||
\n\nCopyright © 2014-2023 Daniel Gultsch
|
||||
\n\nThis program is free software: you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
|
|
@ -42,7 +42,7 @@
|
|||
GNU General Public License for more details.
|
||||
\n\nYou should have received a copy of the GNU General Public License
|
||||
along with this program. If not, see https://www.gnu.org/licenses
|
||||
\n\nDownload the full source code at https://codeberg.org/iNPUTmice/Conversations
|
||||
\n\nDownload the full source code at https://dev.narayana.im/narayana/conversations-classic
|
||||
\n\n\nLibraries
|
||||
\n\nhttps://webrtc.org\nCopyright (c) 2011, The WebRTC project authors. All rights reserved. (https://webrtc.org/support/license)
|
||||
\n\nhttps://github.com/ypresto/android-transcoder\n(Apache License, Version 2.0)
|
||||
|
|
|
|||
Loading…
Reference in a new issue