Conversations Classic: the very last word in instant messaging
+another.im: the very last word in instant messaging
## Design principles @@ -28,11 +28,11 @@ ### XMPP Features -Conversations Classic works with every XMPP server out there. However XMPP is an +another.im 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 Classic supports a couple of these to make the overall user +XEP's. another.im 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 Classic you +support these extensions; therefore to get the most out of another.im 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: @@ -51,7 +51,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-0308: Last Message Correction](https://xmpp.org/extensions/xep-0308.html) allows you to edit last message as well as retract it * [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 Classic was + server. Catch up with messages that were sent while another.im was offline. * [XEP-0352: Client State Indication](http://xmpp.org/extensions/xep-0352.html) lets the server know whether or not Conversations is in the background. Allows the server to save bandwidth by @@ -67,7 +67,7 @@ run your own XMPP server for you and your friends. These XEP's are: #### How do I install Conversations? -Conversations Classic is entirely open source and licensed under GPLv3. So if you are a +another.im 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. @@ -85,12 +85,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 Classic will automatically look up the SRV records for your domain name +another.im 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 Classic. +another.im. #### I get 'Incompatible Server' @@ -101,15 +101,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 Classic is able to handle. Conversations Classic supports +a login (SASL) mechanism that another.im is able to handle. another.im 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 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`. +When trying to connect to OpenFire the bind failure can be a permanent problem when the domain part of the Jabber ID entered in another.im 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`. another.im doesn’t like that. +This can be fixed by creating a new account in another.im 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. @@ -119,10 +119,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.** +**The battery consumption and the entire behavior of another.im 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 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 <= 7.1 or another.im from F-Droid (all Android versions) +The foreground notification is still controlled over the expert settings within another.im 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. @@ -134,20 +134,20 @@ Long press the permanent notification and press the info `(i)` button to get int 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 Classic or can provide you with tips on running your own XMPP server. If +another.im 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 Classic +The address book integration was designed to protect your privacy. another.im 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 Classic will use the name and +add a Jabber ID to your phones address book another.im 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 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 +details within another.im. This will start an "add to address book" intent +with the JID as the payload. This doesn't require another.im to have write permissions on your address book but also doesn't require you to copy/paste a JID from one app to another. @@ -203,21 +203,21 @@ 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 Classic should be an instant messenger for the future and -instead of making Conversations Classic compatible with the past we should work on +adopted. However another.im should be an instant messenger for the future and +instead of making another.im 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 Classic is trying to get rid of old behaviours and set an example for +another.im is trying to get rid of old behaviours and set an example for other clients. -#### How do I backup / move Conversations Classic to a new device? +#### How do I backup / move another.im to a new device? Use the Backup button in the Settings. -#### Conversations Classic is missing a certain feature +#### another.im is missing a certain feature Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im) @@ -231,7 +231,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 Classic is experimental. This is not because it will make the app unstable +another.im 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 @@ -269,12 +269,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 Classic to ensure that. +Right now there is no check in another.im 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 Classic is the only client that uses +feature is regarded experimental. another.im is the only client that uses XEP-0027 with conferences. (The XEP neither specifically allows nor disallows this.) diff --git a/build.gradle b/build.gradle index e7cec89a4..6b9836627 100644 --- a/build.gradle +++ b/build.gradle @@ -109,7 +109,7 @@ android { archivesBaseName += "-$versionName" applicationId "eu.siacs.conversations.classic" resValue "string", "applicationId", applicationId - def appName = "Conversations Classic" + def appName = "another.im" resValue "string", "app_name", appName buildConfigField "String", "APP_NAME", "\"$appName\"" } diff --git a/fastlane/metadata/android/en-US/changelogs/4211004.txt b/fastlane/metadata/android/en-US/changelogs/4211004.txt index b1ceab468..c6027656c 100644 --- a/fastlane/metadata/android/en-US/changelogs/4211004.txt +++ b/fastlane/metadata/android/en-US/changelogs/4211004.txt @@ -1,4 +1,4 @@ -The app is renamed to Conversations Classic. +The app is renamed to another.im. * Numerous small fixes * Info about PM on MUC details screen diff --git a/fastlane/metadata/android/en-US/full_description.txt b/fastlane/metadata/android/en-US/full_description.txt index 7892ba73e..a9813ee5e 100644 --- a/fastlane/metadata/android/en-US/full_description.txt +++ b/fastlane/metadata/android/en-US/full_description.txt @@ -23,7 +23,7 @@ Features: XMPP Features: -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 Classic supports a couple of those 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 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. +another.im works with every XMPP server out there. However XMPP is an extensible protocol. These extensions are standardized as well in so called XEP’s. another.im supports a couple of those 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 another.im 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 XEPs are - as of now: @@ -36,7 +36,7 @@ These XEPs are - as of now: * XEP-0237: Roster Versioning mainly to save bandwidth on poor mobile connections. * 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-0308: Last Message Correction allows you to edit last message as well as retract it. -* XEP-0313: Message Archive Management synchronize message history with the server. Catch up with messages that were sent while Conversations Classic was offline. -* XEP-0352: Client State Indication lets the server know whether or not Conversations Classic is in the background. Allows the server to save bandwidth by withholding unimportant packages. +* XEP-0313: Message Archive Management synchronize message history with the server. Catch up with messages that were sent while another.im was offline. +* XEP-0352: Client State Indication lets the server know whether or not another.im 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. * XEP-0461: Message Replies provides support of native replies, which also works in many transports (gateways) as well. diff --git a/fastlane/metadata/android/ru/changelogs/4211004.txt b/fastlane/metadata/android/ru/changelogs/4211004.txt index 11b67b8d3..773e9a385 100644 --- a/fastlane/metadata/android/ru/changelogs/4211004.txt +++ b/fastlane/metadata/android/ru/changelogs/4211004.txt @@ -1,4 +1,4 @@ -Приложение переименовано в Conversations Classic. +Приложение переименовано в another.im. * Многочисленные мелкие исправления * Информация о личных сообщениях в групповом чате на экране сведений diff --git a/fastlane/metadata/android/ru/full_description.txt b/fastlane/metadata/android/ru/full_description.txt index 39c6708dd..17071e209 100644 --- a/fastlane/metadata/android/ru/full_description.txt +++ b/fastlane/metadata/android/ru/full_description.txt @@ -23,7 +23,7 @@ Функции XMPP: -Conversations Classic работает с любым сервером XMPP. Однако, XMPP — расширяемый протокол. Расширения также стандартизированы в так называемых XEP. Conversations Classic поддерживает некоторые из них, дабы улучшить общий опыт использования. Может оказаться, что Ваш текущий сервер XMPP не поддерживает эти расширения. Поэтому, чтобы получить максимум от Conversations Classic, рассмотрите переход на XMPP-сервер с поддержкой этих расширений, или — ещё лучше — запускайте собственный сервер XMPP для себя и своих друзей. +another.im работает с любым сервером XMPP. Однако, XMPP — расширяемый протокол. Расширения также стандартизированы в так называемых XEP. another.im поддерживает некоторые из них, дабы улучшить общий опыт использования. Может оказаться, что Ваш текущий сервер XMPP не поддерживает эти расширения. Поэтому, чтобы получить максимум от another.im, рассмотрите переход на XMPP-сервер с поддержкой этих расширений, или — ещё лучше — запускайте собственный сервер XMPP для себя и своих друзей. В настоящее время поддерживаются такие XEP: @@ -36,7 +36,7 @@ Conversations Classic работает с любым сервером XMPP. Од * XEP-0237: Версионирование Списка Контактов, прежде всего для сберегания мобильного трафика. * XEP-0280: Сообщения под Копирку, автоматически синхронизирует отправленные сообщений на настольный клиент, чем позволяет плавно переключаться между мобильным и настольным клиентами в рамках одного разговора. * XEP-0308: Исправление Последнего Сообщения, позволяет отредактировать или отозвать сообщение. -* XEP-0313: Управление Архивом Сообщений, синхронизирует историю сообщений с сервером. Узнавайте о сообщениях, отправленных, пока Conversations Classic находился оффлайн. -* XEP-0352: Индикация Состояния Клиента, сообщает серверу, работает ли Conversations Classic в фоновом режиме. Позволяет серверу сберегать пропускную способность, удерживая неважные пакеты. +* XEP-0313: Управление Архивом Сообщений, синхронизирует историю сообщений с сервером. Узнавайте о сообщениях, отправленных, пока another.im находился оффлайн. +* XEP-0352: Индикация Состояния Клиента, сообщает серверу, работает ли another.im в фоновом режиме. Позволяет серверу сберегать пропускную способность, удерживая неважные пакеты. * XEP-0363: Загрузка Файлов по HTTP, позволяет обмениваться файлами в конференциях и с оффлайн-контактами. Требует дополнительного компонента на Вашем сервере. * XEP-0461: Ответы на Сообщения, предоставляет поддержку привязанных к сообщению ответов, которые также работают со многими транспортами (мостами). diff --git a/fastlane/metadata/android/uk/changelogs/4211004.txt b/fastlane/metadata/android/uk/changelogs/4211004.txt index b08f436dd..56447144d 100644 --- a/fastlane/metadata/android/uk/changelogs/4211004.txt +++ b/fastlane/metadata/android/uk/changelogs/4211004.txt @@ -1,4 +1,4 @@ -Застосунок перейменовано на Conversations Classic. +Застосунок перейменовано на another.im. * Численні дрібні виправлення * Інформація про особисті повідомлення в груповому чаті на екрані деталей diff --git a/fastlane/metadata/android/uk/full_description.txt b/fastlane/metadata/android/uk/full_description.txt index 55c7fcc8b..bdb93ca0f 100644 --- a/fastlane/metadata/android/uk/full_description.txt +++ b/fastlane/metadata/android/uk/full_description.txt @@ -23,7 +23,7 @@ Функції XMPP: -Conversations Classic працює з будь-яким сервером XMPP. Проте XMPP — розширюваний протокол. Розширення також стандартизовані в так званих XEP. Conversations Classic підтримує кілька з них, щоб покращити загальний досвід користування. Може виявитися, що Ваш поточний сервер XMPP не підтримує цих розширень. Тому, щоб отримати максимум від Conversations Classic, розгляньте перехід на XMPP-сервер з підтримкою цих розширень або — ще краще — запускайте власний сервер XMPP для себе і своїх друзів. +another.im працює з будь-яким сервером XMPP. Проте XMPP — розширюваний протокол. Розширення також стандартизовані в так званих XEP. another.im підтримує кілька з них, щоб покращити загальний досвід користування. Може виявитися, що Ваш поточний сервер XMPP не підтримує цих розширень. Тому, щоб отримати максимум від another.im, розгляньте перехід на XMPP-сервер з підтримкою цих розширень або — ще краще — запускайте власний сервер XMPP для себе і своїх друзів. На даний час підтримуються такі XEP: @@ -36,7 +36,7 @@ Conversations Classic працює з будь-яким сервером XMPP. * XEP-0237: Версіонування Списку Контактів, передусім для заощадження мобільного трафіку. * XEP-0280: Повідомлення під Копірку, автоматично синхронізує надіслані повідомлення на настільний клієнт, чим дозволяє плавно перемикатися між мобільним і настільним клієнтами в рамках однієї розмови. * XEP-0308: Виправлення Останнього Повідомлення, дозволяє відредагувати чи відкликати повідомлення. -* XEP-0313: Керування Архівом Повідомлень, синхронізує історію повідомлень із сервером. Дізнавайтеся про повідомлення, надіслані, поки Conversations Classic був офлайн. -* XEP-0352: Індикація Стану Клієнта, повідомляє серверу, чи працює Conversations Classic у фоновому режимі. Дозволяє серверу заощаджувати пропускну здатність, утримуючи неважливі пакети. +* XEP-0313: Керування Архівом Повідомлень, синхронізує історію повідомлень із сервером. Дізнавайтеся про повідомлення, надіслані, поки another.im був офлайн. +* XEP-0352: Індикація Стану Клієнта, повідомляє серверу, чи працює another.im у фоновому режимі. Дозволяє серверу заощаджувати пропускну здатність, утримуючи неважливі пакети. * XEP-0363: Завантаження Файлів за HTTP, дозволяє обмінюватися файлами в конференціях і з офлайн-контактами. Потребує додаткового компонента на Вашому сервері. * XEP-0461: Відповіді на Повідомлення, надає підтримку привʼязаних до повідомлення відповідей, які також працюють із багатьма транспортами (мостами). diff --git a/src/conversations/res/.DS_Store b/src/conversations/res/.DS_Store new file mode 100644 index 000000000..746f05cb8 Binary files /dev/null and b/src/conversations/res/.DS_Store differ diff --git a/src/conversations/res/drawable-anydpi/ic_notification.xml b/src/conversations/res/drawable-anydpi/ic_notification.xml new file mode 100644 index 000000000..c469e6d3f --- /dev/null +++ b/src/conversations/res/drawable-anydpi/ic_notification.xml @@ -0,0 +1,22 @@ +