Merge pull request 'more accurate uk translation' (#26) from develop into master

Reviewed-on: #26

FAQ.md

@@ -0,0 +1,224 @@
+# FAQ
+
+## General
+
+### How do I install another.im?
+
+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.
+
+### 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  [another.im](https://another.im). If you don’t like to use *another.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 another.im to create an account. Just select *register new account* on server within the create account dialog.
+
+#### Domain hosting
+Using your own domain not only gives you a more recognizable Jabber ID, it also gives you the flexibility to migrate your account between different XMPP providers. This is a good compromise between the responsibilities of having to operate your own server and the downsides of being dependent on a single provider.
+
+#### Running your own
+If you already have a server somewhere and are willing and able to put the necessary work in you can run your own XMPP server.
+
+As of 2023 XMPP has reached a level of maturity where all major XMPP servers ([ejabberd](https://ejabberd.im), [Prosody](https://prosody.im), [Openfire](https://www.igniterealtime.org/projects/openfire/), [Tigase](https://tigase.net/xmpp-server/)) should work well with another.im.
+
+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
+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
+another.im.
+
+### I get 'Incompatible Server'
+
+As regular user you should be picking a different server. The server you selected
+is probably insecure and/or very old.
+
+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 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 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.
+
+Maybe you attempted to use the Jabber ID `test@b.tld` because `a.tld` doesn’t point to the correct host. In that case you might have to enable the extended connection settings in the expert settings of another.im and set a host name.
+
+### I get 'Stream opening error'. What does that mean?
+
+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 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 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 another.im (and other apps) using battery. Starting with Android 8.1 you can disable that notification again with the same method described above.
+
+#### 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.
+
+### another.im doesn’t work for me. Where can I get help?
+
+You can join our conference room on [`xmppclient-dev@conference.another.im`](xmpp:xmppclient-dev@conference.another.im).
+A lot of people in there are able to answer basic questions about the usage of
+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. 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 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 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.
+
+### I get 'delivery failed' on my messages
+
+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.
+
+Instead of returning a message to the sender both ejabberd and prosody have the
+ability to store messages in offline storage when the disconnecting client is
+the only client. In prosody this is available via an extra module called
+```mod_smacks_offline```. In ejabberd this is available via some configuration
+settings.
+
+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.
+
+### Where can I see the status of my contacts? How can I set a status or priority?
+
+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 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
+another.im is trying to get rid of old behaviours and set an example for
+other clients.
+
+
+### How do I backup / move another.im to a new device?
+
+Use the Backup button in the Settings.
+
+### another.im is missing a certain feature
+
+Please report it to our XMPP conference [`xmppclient-dev@conference.another.im`](xmpp:xmppclient-dev@conference.another.im).
+
+## Security
+
+### Why are there two end-to-end encryption methods and which one should I choose?
+
+* 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](http://xmpp.org/extensions/xep-0363.html). However, OMEMO not widely support and is currently implemented only [by a handful of clients](https://omemo.top).
+* OpenPGP (XEP-0027) is a very old encryption method that has some advantages over OMEMO but should only be used by people who know what they are doing.
+
+### How do I use OpenPGP
+
+Before you continue reading you should note that the OpenPGP support in
+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
+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 and it is rather verbose.
+
+To use OpenPGP you have to install the open source app
+[OpenKeychain](http://www.openkeychain.org) and then long press on the account in
+manage accounts and choose renew PGP announcement from the contextual menu.
+
+### OMEMO is grayed out. What do I do?
+OMEMO is only available in 1:1 chats and private (members-only, non-anonymous) group chats. Encrypting public group chats makes little to no sense since anyone (including a hypothetical attacker) can join and a user couldn’t possibily verify all participants anyway. Furthermore for a lot of public group chat it is desirable to give new comers access to the full history.
+
+### OMEMO doesn’t work. I get a 'Something went wrong' message in the 'Trust OMEMO Fingerprints' screen.
+OMEMO has two requirements: Your server and the server of your contact need to support PEP. Both of you can verify that individually by opening your account details and selecting ```Server info``` from the menu. The appearing table should list PEP as available. The second requirement is that the initial sender needs to have access to the published key material. This can either be achieved by having mutual presence subscription (you can verify that by opening the contact details and see if both check boxes *Send presence updates* and *Receive presence updates* are checked) or by using a server that makes the public key material accessible to anyone. In the [Compliance Tester](https://compliance.conversations.im) this is indicated by the 'OMEMO' feature. Since it is very common that the first messages are exchanged *before* adding each other to the contact list it is desirable to use servers that have 'OMEMO support'.
+
+### How does the encryption for group chats work?
+
+#### OMEMO
+
+OMEMO encryption works only in private (members only) conferences that are non-anonymous. Non-anonymous (being able to discover the real JID of other participants) is a technical requirement to discover the key material. Members only is a sort of arbitrary requirement imposed by another.im. (see 'OMEMO is grayed out')
+
+The server of all participants need to pass the OMEMO [Compliance Test](https://conversations.im/compliance/).
+In other words they either need to run ejabberd 18.01+ or Prosody 0.11+.
+
+(Alternatively it would also work if all participants had each other in their contact list; But that rarely is the case in larger group chats.)
+
+The owner of a conference can make a public conference private by going into the conference
+details and hit the settings button (the one with the gears) and select both *private* and
+*members only*.
+
+#### OpenPGP
+
+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 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. another.im is the only client that uses
+XEP-0027 with conferences. (The XEP neither specifically allows nor disallows
+this.)
+
+### What is Blind Trust Before Verification / why are messages marked with a red lock?
+
+Read more about the concept on https://gultsch.de/trust.html
+
+### I found a bug
+
+Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im).

README.md

@@ -1,6 +1,44 @@
-<h1 align="center">Conversations Classic</h1>
+<h1 align="center">another.im</h1>
 
-<p align="center">Conversations Classic: the very last word in instant messaging</p>
+<h2><p align="center">another.im: the very last word in instant messaging</p></h2>
+
+<p align="center"><a href="https://f-droid.org/packages/im.narayana.another"> 
+    <img src="https://fdroid.gitlab.io/artwork/badge/get-it-on.png"
+    alt="Get it on F-Droid"
+    height="80">
+</a></p>
+
+## About app and us 
+
+the Another Instant Messenger is not a messenger,
+> don't believe the words.
+
+
+we just offer you a standardized xmpp-client with predicted features which work equally on all platforms.\
+in our clients we have realized pure XMPP and you won't step on a hedgehog unexpectedly when you communicate with another xmpp client or server.
+
+
+because you buy our open-sourced bitcoin,\
+we decided to offer you to buy our open-sourced messenger.\
+ha-ha joke.\
+it's free, really. GPLv3, whatever.
+
+
+for Android, it's just an improved fork of Conversations,\
+for iOS, it's our development from scratch,\
+for Desktops we're polako [looking](xmpp:xmppclient-dev@conference.another.im). for devs.
+
+
+all necessary XEP's was realized by Conversations devs but we added a cherry on top of this.\
+on the server side we are offering free to use Prosody server,\
+just connect to [another.im](xmpp:xmppclient-dev@conference.another.im), but we are encouroge you to don't trust us, self-host.
+
+OTR encryption is also supported as 'secret chats' due to otr has been designed for one-time sessions and the concept of 'secret chats' fully corresponds to the idea of the OTR.
+
+also you can just download <a href="https://dev.narayana.im/narayana/anotherim">the source code</a>, compile it and install.
+
+only those who seeks will realize the way to pay us,\
+we can offer you additional server-side features and some telecommunication magic on our <a href="https://narayana.im">narayana.im</a>
 
 ## Design principles
 
@@ -28,14 +66,15 @@
 
 ### XMPP Features
 
-Conversations 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 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 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:
 
+* [XEP-0050: Ad-Hoc Commands](http://xmpp.org/extensions/xep-0050.html) lets to interact with gateways
 * [XEP-0065: SOCKS5 Bytestreams](http://xmpp.org/extensions/xep-0065.html) will be used to transfer
   files if both parties are behind a firewall (NAT).
 * [XEP-0163: Personal Eventing Protocol](http://xmpp.org/extensions/xep-0163.html) for avatars and OMEMO.
@@ -44,268 +83,24 @@ run your own XMPP server for you and your friends. These XEP's are:
 * [XEP-0198: Stream Management](http://xmpp.org/extensions/xep-0198.html) allows XMPP to survive small network outages and
   changes of the underlying TCP connection.
 * [XEP-0215: External Service Discovery](https://xmpp.org/extensions/xep-0215.html) will be used to discover STUN and TURN servers which facilitate P2P A/V calls.
+* [XEP-0237: Roster Versioning](http://xmpp.org/extensions/xep-0237.html) mainly to save bandwidth on poor mobile connections
 * [XEP-0280: Message Carbons](http://xmpp.org/extensions/xep-0280.html) 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](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
-  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-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 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
   withholding unimportant packages.
 * [XEP-0363: HTTP File Upload](http://xmpp.org/extensions/xep-0363.html) allows you to share files in conferences
   and with offline contacts.
 * [XEP-0461: Message Replies](https://xmpp.org/extensions/xep-0461.html) provides support of native replies, which also works in many transports (gateways) as well
+* [XEP-0364: Current Off-the-Record Messaging Usage](https://xmpp.org/extensions/xep-0364.html) is also supported as 'secret chats' due to otr has been designed for one-time sessions and the concept of 'secret chats' fully corresponds to the idea of the OTR.
 
+### FAQ
 
-## FAQ
+[*FAQ*](/FAQ.md) is located separately and may contain links to upstream. 
 
-### General
+*In case of issues, bugs, suggestions please contact us directly [`xmppclient-dev@conference.another.im`](xmpp:xmppclient-dev@conference.another.im).*
-
-#### How do I install Conversations?
-
-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 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.
-
-##### Domain hosting
-Using your own domain not only gives you a more recognizable Jabber ID, it also gives you the flexibility to migrate your account between different XMPP providers. This is a good compromise between the responsibilities of having to operate your own server and the downsides of being dependent on a single provider.
-
-##### Running your own
-If you already have a server somewhere and are willing and able to put the necessary work in you can run your own XMPP server.
-
-As of 2023 XMPP has reached a level of maturity where all major XMPP servers ([ejabberd](https://ejabberd.im), [Prosody](https://prosody.im), [Openfire](https://www.igniterealtime.org/projects/openfire/), [Tigase](https://tigase.net/xmpp-server/)) should work well with Conversations.
-
-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
-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.
-
-#### I get 'Incompatible Server'
-
-As regular user you should be picking a different server. The server you selected
-is probably insecure and/or very old.
-
-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
-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`. 
-
-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.
-
-Maybe you attempted to use the Jabber ID `test@b.tld` because `a.tld` doesn’t point to the correct host. In that case you might have to enable the extended connection settings in the expert settings of Conversations and set a host name.
-
-#### I get 'Stream opening error'. What does that mean?
-
-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).
-
-
-#### 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 &lt;= 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 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.
-
-##### 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
-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
-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.
-
-#### I get 'delivery failed' on my messages
-
-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.
-
-Instead of returning a message to the sender both ejabberd and prosody have the
-ability to store messages in offline storage when the disconnecting client is
-the only client. In prosody this is available via an extra module called
-```mod_smacks_offline```. In ejabberd this is available via some configuration
-settings.
-
-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.
-
-#### Where can I see the status of my contacts? How can I set a status or priority?
-
-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.
-
-
-#### How do I backup / move Conversations to a new device?
-
-Use the Backup button in the Settings.
-
-#### Conversations is missing a certain feature
-
-Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im  
-
-### Security
-
-#### Why are there two end-to-end encryption methods and which one should I choose?
-
-* 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](http://xmpp.org/extensions/xep-0363.html). However, OMEMO not widely support and is currently implemented only [by a handful of clients](https://omemo.top).
-* OpenPGP (XEP-0027) is a very old encryption method that has some advantages over OMEMO but should only be used by people who know what they are doing.
-
-#### 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
-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 and it is rather verbose.
-
-To use OpenPGP you have to install the open source app
-[OpenKeychain](http://www.openkeychain.org) and then long press on the account in
-manage accounts and choose renew PGP announcement from the contextual menu.
-
-#### OMEMO is grayed out. What do I do?
-OMEMO is only available in 1:1 chats and private (members-only, non-anonymous) group chats. Encrypting public group chats makes little to no sense since anyone (including a hypothetical attacker) can join and a user couldn’t possibily verify all participants anyway. Furthermore for a lot of public group chat it is desirable to give new comers access to the full history.
-
-#### OMEMO doesn’t work. I get a 'Something went wrong' message in the 'Trust OMEMO Fingerprints' screen.
-OMEMO has two requirements: Your server and the server of your contact need to support PEP. Both of you can verify that individually by opening your account details and selecting ```Server info``` from the menu. The appearing table should list PEP as available. The second requirement is that the initial sender needs to have access to the published key material. This can either be achieved by having mutual presence subscription (you can verify that by opening the contact details and see if both check boxes *Send presence updates* and *Receive presence updates* are checked) or by using a server that makes the public key material accessible to anyone. In the [Compliance Tester](https://compliance.conversations.im) this is indicated by the 'OMEMO' feature. Since it is very common that the first messages are exchanged *before* adding each other to the contact list it is desirable to use servers that have 'OMEMO support'.
-
-#### How does the encryption for group chats work?
-
-##### OMEMO
-
-OMEMO encryption works only in private (members only) conferences that are non-anonymous. Non-anonymous (being able to discover the real JID of other participants) is a technical requirement to discover the key material. Members only is a sort of arbitrary requirement imposed by Conversations. (see 'OMEMO is grayed out')
-
-The server of all participants need to pass the OMEMO [Compliance Test](https://conversations.im/compliance/).
-In other words they either need to run ejabberd 18.01+ or Prosody 0.11+.
-
-(Alternatively it would also work if all participants had each other in their contact list; But that rarely is the case in larger group chats.)
-
-The owner of a conference can make a public conference private by going into the conference
-details and hit the settings button (the one with the gears) and select both *private* and
-*members only*.
-
-##### OpenPGP
-
-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.)
-
-#### What is Blind Trust Before Verification / why are messages marked with a red lock?
-
-Read more about the concept on https://gultsch.de/trust.html
-
-#### I found a bug
-
-Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im). 

build.gradle

@@ -18,20 +18,12 @@ apply plugin: 'org.jetbrains.kotlin.android'
 repositories {
     google()
     mavenCentral()
-    jcenter()
     maven { url='https://jitpack.io'}
 }
 
 configurations {
-    playstoreImplementation
     freeImplementation
     conversationsFreeImplementation
-    conversationsPlaystorImplementation
-    conversationsPlaystoreImplementation
-    quicksyPlaystoreImplementation
-    quicksyPlaystoreImplementation
-    quicksyFreeImplementation
-    quicksyImplementation
 }
 
 dependencies {
@@ -39,13 +31,6 @@ dependencies {
 
     implementation 'androidx.viewpager:viewpager:1.0.0'
 
-    playstoreImplementation('com.google.firebase:firebase-messaging:23.3.1') {
-        exclude group: 'com.google.firebase', module: 'firebase-core'
-        exclude group: 'com.google.firebase', module: 'firebase-analytics'
-        exclude group: 'com.google.firebase', module: 'firebase-measurement-connector'
-    }
-    conversationsPlaystoreImplementation("com.android.installreferrer:installreferrer:2.2")
-    quicksyPlaystoreImplementation 'com.google.android.gms:play-services-auth-api-phone:18.0.1'
     implementation 'com.github.open-keychain.open-keychain:openpgp-api:v5.7.1'
     implementation("com.github.CanHub:Android-Image-Cropper:2.2.0")
     implementation 'androidx.appcompat:appcompat:1.6.1'
@@ -86,17 +71,20 @@ dependencies {
     implementation 'com.google.guava:guava:32.1.3-android'
     implementation 'io.michaelrocks:libphonenumber-android:8.13.17'
     implementation 'im.conversations.webrtc:webrtc-android:119.0.0'
+    implementation 'org.jitsi:org.otr4j:0.23'
 
     implementation 'androidx.constraintlayout:constraintlayout:2.1.4'
     implementation "androidx.recyclerview:recyclerview:1.2.1"
     implementation 'com.github.bumptech.glide:glide:4.15.1'
-    implementation 'info.androidhive:imagefilters:1.0.7'
+    // https://mvnrepository.com/artifact/info.androidhive/imagefilters
+    implementation 'com.github.zomato:androidphotofilters:1.0.2'
     implementation 'com.github.chrisbanes:PhotoView:2.3.0'
 
     //implementation 'com.splitwise:tokenautocomplete:3.0.2'
 
     implementation 'com.github.singpolyma:TokenAutoComplete:bfa93780e0'
 
+    implementation 'com.github.kizitonwose.colorpreference:core:1.1.0'
     implementation 'com.github.kizitonwose.colorpreference:support:1.1.0'
     implementation 'com.caverock:androidsvg-aar:1.4'
     implementation 'com.github.singpolyma:Better-Link-Movement-Method:4df081e1e4'
@@ -116,12 +104,12 @@ android {
     defaultConfig {
         minSdkVersion 24
         targetSdkVersion 34
-        versionCode 42113
+        versionCode 2
-        versionName "2.3.0"
+        versionName "1.0.1"
         archivesBaseName += "-$versionName"
-        applicationId "eu.siacs.conversations.classic"
+        applicationId "im.narayana.another"
         resValue "string", "applicationId", applicationId
-        def appName = "Conversations Classic"
+        def appName = "another.im"
         resValue "string", "app_name", appName
         buildConfigField "String", "APP_NAME", "\"$appName\""
     }
@@ -154,58 +142,22 @@ android {
     flavorDimensions += "distribution"
 
     productFlavors {
-
-        quicksy {
-            dimension "mode"
-            applicationId = "im.quicksy.client"
-            resValue "string", "applicationId", applicationId
-
-            def appName = "Quicksy"
-            resValue "string", "app_name", appName
-            buildConfigField "String", "APP_NAME", "\"$appName\""
-        }
-
         conversations {
             dimension "mode"
         }
 
-        playstore {
-            dimension "distribution"
-            versionNameSuffix "+playstore"
-        }
         free {
             dimension "distribution"
-            versionNameSuffix "+free"
+            //versionNameSuffix "+free"
         }
     }
 
     sourceSets {
-        quicksyFree {
-            java {
-                srcDir 'src/quicksyFree/java'
-            }
-        }
-        quicksyPlaystore {
-            java {
-                srcDir 'src/quicksyPlaystore/java'
-            }
-            res {
-                srcDir 'src/quicksyPlaystore/res'
-            }
-        }
         conversationsFree {
             java {
                 srcDir 'src/conversationsFree/java'
             }
         }
-        conversationsPlaystore {
-            java {
-                srcDir 'src/conversationsPlaystore/java'
-            }
-            res {
-                srcDir 'src/conversationsPlaystore/res'
-            }
-        }
     }
 
     buildTypes {

conversations.doap

@@ -5,22 +5,22 @@
          xmlns:foaf="http://xmlns.com/foaf/0.1/"
          xmlns:xmpp="https://linkmauve.fr/ns/xmpp-doap#"
          xmlns:schema="https://schema.org/">
-    <name>Conversations</name>
+    <name>another.im</name>
 
     <created>2014-01-14</created>
 
     <shortdesc xml:lang="en">Android XMPP Client</shortdesc>
 
-    <description xml:lang="en">Conversations is an open source XMPP/Jabber client for the Android platform</description>
+    <description xml:lang="en">another.im is an open source XMPP/Jabber client for the Android platform forked from Conversations</description>
 
-    <homepage rdf:resource="https://conversations.im/"/>
+    <homepage rdf:resource="https://another.im/"/>
-    <download-page rdf:resource="https://play.google.com/store/apps/details?id=eu.siacs.conversations"/>
+    <!--<download-page rdf:resource="https://play.google.com/store/apps/details?id=eu.siacs.conversations"/> -->
-    <bug-database rdf:resource="https://codeberg.org/iNPUTmice/Conversations/issues"/>
+    <bug-database rdf:resource="https://dev.narayana.im/narayana/anotherim/issues"/>
     <!-- See https://github.com/ewilderj/doap/issues/53 -->
-    <developer-forum rdf:resource="xmpp:conversations@siacs.conference.eu?join"/>
+    <developer-forum rdf:resource="xmpp:xmppclient-dev@conference.another.im"/>
-    <support-forum rdf:resource="xmpp:conversations@siacs.conference.eu?join"/>
+    <support-forum rdf:resource="xmpp:xmppclient-dev@conference.another.im"/>
 
-    <license rdf:resource="https://codeberg.org/iNPUTmice/Conversations/src/branch/master/LICENSE"/>
+    <license rdf:resource="https://dev.narayana.im/narayana/anotherim/src/branch/master/LICENSE"/>
 
     <!-- See https://github.com/ewilderj/doap/issues/49 -->
     <language>en</language>
@@ -46,8 +46,8 @@
 
     <maintainer>
         <foaf:Person>
-            <foaf:name>Daniel Gultsch</foaf:name>
+            <foaf:name>kosyak</foaf:name>
-            <foaf:homepage rdf:resource="https://gultsch.de/"/>
+            <foaf:homepage rdf:resource="https://another.im/"/>
         </foaf:Person>
     </maintainer>
 
@@ -63,6 +63,14 @@
     <implements rdf:resource="https://xmpp.org/rfcs/rfc6122.html"/>
     <implements rdf:resource="https://xmpp.org/rfcs/rfc7590.html"/>
 
+    <implements>
+        <xmpp:SupportedXep>
+            <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0364.html"/>
+            <xmpp:status>Deferred</xmpp:status>
+            <xmpp:version>0.3.2</xmpp:version>
+        </xmpp:SupportedXep>
+    </implements>
+
     <implements>
         <xmpp:SupportedXep>
             <xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0027.html"/>

fastlane/metadata/android/de-DE/changelogs/349.txt

@@ -1,4 +0,0 @@
-* Einführung einer Experteneinstellung zur Channel-Erkennung auf dem lokalen Server anstelle von search.jabber.network
-* Standardmäßig Zustellungshäkchen aktiviert und Einstellung entfernt
-* Standardmäßig 'Sendetaste zeigt Status an' aktiviert und die Einstellung entfernt
-* Einstellungen für Sicherung und Vordergrunddienst in den Hauptbereich verschoben

fastlane/metadata/android/de-DE/changelogs/351.txt

@@ -1,3 +0,0 @@
-* Fehlerkorrektur für Jingle IBB Dateitransfer
-* Fehlerkorrektur für wiederholende Korrekturen, welche die Datenbank füllen
-* Wechsel zu Last Message Correction v1.1

fastlane/metadata/android/de-DE/changelogs/353.txt

@@ -1,4 +0,0 @@
-* Benutzer können ihren eigenen Nicknamen festlegen
-* Wiederaufnahme des Downloads von OMEMO-verschlüsselten Dateien
-* Channels verwenden jetzt '#' als Symbol im Profilbild
-* Quicksy verwendet 'immer' als OMEMO-Verschlüsselungsstandard (versteckt das Schlosssymbol)

fastlane/metadata/android/de-DE/changelogs/360.txt

@@ -1 +0,0 @@
-* Unterstützung für ?register und ?register;preauth XMPP URI-Parameter

fastlane/metadata/android/de-DE/changelogs/362.txt

@@ -1 +0,0 @@
-* Unterstützung für automatischen Designwechsel in Android 10

fastlane/metadata/android/de-DE/changelogs/364.txt

@@ -1,2 +0,0 @@
-* Bereitstellen von PDF-Vorschau ab Android 5+
-* Nutzung von 12 byte IVs für OMEMO

fastlane/metadata/android/de-DE/changelogs/367.txt

@@ -1,2 +0,0 @@
-* Profilbildauswahl auf einigen Android 10 Geräten korrigiert
-* Dateiübertragung für größere Dateien korrigiert

fastlane/metadata/android/de-DE/changelogs/379.txt

@@ -1 +0,0 @@
-* Audio-/Videoanrufe (erfordert Serverunterstützung in Form von STUN- und TURN-Servern, die über XEP-0215 ermittelt werden können)

fastlane/metadata/android/de-DE/changelogs/381.txt

@@ -1,2 +0,0 @@
-* Akustische Rückmeldungen (Wählen, Anruf begonnen, Anruf beendet) für Audioanrufe
-* Problem mit der Wiederholung eines fehlgeschlagenen Videoanrufs behoben

fastlane/metadata/android/de-DE/changelogs/382.txt

@@ -1,2 +0,0 @@
-* Schaltfläche zum Umschalten der Kamera während eines Videoanrufs hinzugefügt
-* Audioanrufe auf Tablets repariert

fastlane/metadata/android/de-DE/changelogs/383.txt

@@ -1,3 +0,0 @@
-* Anrufsymbol nach links verschoben, damit die anderen Symbole der Symbolleiste an einer einheitlichen Stelle bleiben
-* Anzeige der Gesprächsdauer bei Sprachanrufen
-* Unterbrechung der Verbindung bei A/V-Anrufen (zwei Personen rufen sich gleichzeitig an)

fastlane/metadata/android/de-DE/changelogs/387.txt

@@ -1,2 +0,0 @@
-* Überarbeitung der UI für die Anmeldung mit Zertifikat
-* Integration der Möglichkeit, Chats ganz oben anzuheften (zu den Favoriten hinzufügen)

fastlane/metadata/android/de-DE/changelogs/388.txt

@@ -1,3 +0,0 @@
-* Reduzierung des Echos bei Anrufen auf einigen Geräten
-* Anmeldung korrigiert, wenn Passwörter Sonderzeichen enthalten
-* Wähl- und Besetztzeichen bei Videoanrufen auf dem Lautsprecher abspielen

fastlane/metadata/android/de-DE/changelogs/390.txt

@@ -1 +0,0 @@
-* Möglichkeit zur Aufnahme einer Sprachnachricht, wenn der Anrufer beschäftigt ist

fastlane/metadata/android/de-DE/changelogs/393.txt

@@ -1,3 +0,0 @@
-* Hilfe-Schaltfläche anzeigen, wenn A/V-Anruf fehlschlägt
-* Einige lästige Abstürze behoben
-* Jingle-Verbindungen (Dateiübertragung + Anrufe) mit bloßen JIDs behoben

fastlane/metadata/android/de-DE/changelogs/394.txt

@@ -1,2 +0,0 @@
-* Benachrichtigungen wurden unter bestimmten Bedingungen nicht mehr angezeigt
-* Kompatibilitätsprobleme und Abstürze im Zusammenhang mit A/V-Anrufen behoben

fastlane/metadata/android/de-DE/changelogs/395.txt

@@ -1,3 +0,0 @@
-* Hinzufügen von 'Zurück zum Chat' zum Audio-Anruf-Bildschirm
-* Verbesserung der Tastaturkürzel
-* Fehlerbehebungen

fastlane/metadata/android/de-DE/changelogs/397.txt

@@ -1,3 +0,0 @@
-* Verarbeitung von GPX-Dateien
-* Verbesserte Leistung bei der Wiederherstellung von Sicherungen
-* Fehlerbehebungen

fastlane/metadata/android/de-DE/changelogs/398.txt

@@ -1,4 +0,0 @@
-* Suche in einzelnen Unterhaltungen
-* Benutzer werden benachrichtigt, wenn die Nachrichtenzustellung fehlschlägt
-* Anzeigenamen (Nicks) von Quicksy-Benutzern über Neustarts hinweg speichern
-* Hinzufügen einer Schaltfläche zum Starten von Orbot (Tor) aus der Benachrichtigung heraus, falls erforderlich

fastlane/metadata/android/de-DE/changelogs/401.txt

@@ -1,2 +0,0 @@
-* Suche auf Android <= 5 korrigiert
-* Optimierung des Speicherverbrauchs

fastlane/metadata/android/de-DE/changelogs/402.txt

@@ -1,3 +0,0 @@
-* Bietet einfache Einladungserstellung auf unterstützenden Servern
-* GIFs anzeigen, die von Movim gesendet werden
-* Profilbilder im Cache speichern

fastlane/metadata/android/de-DE/changelogs/403.txt

@@ -1,3 +0,0 @@
-* Behebung von Verbindungsproblemen, wenn verschiedene Konten unterschiedliche SCRAM-Mechanismen verwenden
-* Unterstützung für SCRAM-SHA-512 hinzugefügt
-* P2P (Jingle) Dateiübertragung mit eigenem Kontakt zulassen

fastlane/metadata/android/de-DE/changelogs/404.txt

@@ -1 +0,0 @@
-* Kleinere Stabilitätsverbesserungen für A/V-Anrufe

fastlane/metadata/android/de-DE/changelogs/405.txt

@@ -1 +0,0 @@
-* Quicksy: Automatischer Empfang der Bestätigungs-SMS

fastlane/metadata/android/de-DE/changelogs/407.txt

@@ -1,3 +0,0 @@
-* Anzeige der Anruftaste für Offline-Kontakte, wenn diese zuvor Unterstützung gemeldet haben
-* Zurück-Taste beendet den Anruf nicht mehr, wenn der Anruf gerade läuft
-* Fehlerbehebungen

fastlane/metadata/android/de-DE/changelogs/42000.txt

@@ -1,4 +0,0 @@
-* Möglichkeit zur Auswahl des Klingeltons für eingehende Anrufe
-* Behebung der OpenPGP-Schlüsselerkennung für OpenKeychain 5.6+
-* Korrekte Verifizierung von Punycode-TLS-Zertifikaten
-* Verbesserte Stabilität des RTP-Sitzungsaufbaus (Anrufe)

fastlane/metadata/android/de-DE/changelogs/42006.txt

@@ -1,2 +0,0 @@
-* Verifizierung von A/V-Anrufen mit bereits bestehenden OMEMO-Sitzungen
-* Verbesserung der Kompatibilität mit WebRTC-Implementierungen, die nicht von libwebrtc stammen

fastlane/metadata/android/de-DE/changelogs/42010.txt

@@ -1,2 +0,0 @@
-* Verschiedene Fehlerbehebungen rund um die Tor-Unterstützung
-* Verbesserung der Anrufkompatibilität mit Dino

fastlane/metadata/android/de-DE/changelogs/42012.txt

@@ -1 +0,0 @@
-* Problembehebung beim HTTP-Upload/Download für Benutzer, die den System-CAs nicht vertrauen

fastlane/metadata/android/de-DE/changelogs/42013.txt

@@ -1 +0,0 @@
-* Probleme mit "Keine Verbindung" unter Android 7.1 behoben

fastlane/metadata/android/de-DE/changelogs/42014.txt

@@ -1,2 +0,0 @@
-* Domänenname immer überprüfen. Kein Überschreiben von Benutzern
-* Unterstützung der Kontaktlisten-Vorauthentifizierung

fastlane/metadata/android/de-DE/changelogs/42015.txt

@@ -1 +0,0 @@
-* Kleinere A/V-Verbesserungen

fastlane/metadata/android/de-DE/changelogs/42018.txt

@@ -1,3 +0,0 @@
-* Schwarze Balken anzeigen, wenn das entfernte Video nicht dem Seitenverhältnis des Bildschirms entspricht
-* Verbesserung der Suchleistung
-* Einstellung hinzugefügt, um Bildschirmfotos zu verhindern

fastlane/metadata/android/de-DE/changelogs/42022.txt

@@ -1,2 +0,0 @@
-* Fehler behoben, bei dem einige Videos nicht komprimiert wurden
-* Seltenen Absturz beim Öffnen von Benachrichtigungen behoben

fastlane/metadata/android/de-DE/changelogs/42023.txt

@@ -1,2 +0,0 @@
-* Absturz beim Rendern einiger Anführungszeichen behoben
-* Absturz im Willkommensbildschirm behoben

fastlane/metadata/android/de-DE/changelogs/42037.txt

@@ -1,9 +0,0 @@
-* Abfrage der Bluetooth-Berechtigung bei A/V-Anrufen (nur bei Bluetooth-Headsets erforderlich)
-* Fehler beim Anrufen von Movim behoben
-* Anzeige eines falschen Profilbilds bei Gruppenchats behoben
-* Immer nach dem Opt-Out für Akku-Optimierungen fragen
-* Interaktion mit Google Maps Share Location Plugin behoben
-* Fußnote bezüglich der Servergebühr entfernt
-* Dateien an einem für Android 11 geeigneten Ort speichern
-* Anruf nach Netzwechsel erneut versuchen zu verbinden
-* JID des Anrufers und JID des Kontos im Bildschirm für eingehende Anrufe anzeigen

fastlane/metadata/android/de-DE/changelogs/42038.txt

@@ -1,2 +0,0 @@
-* Kleinere Fehlerbehebungen
-* Wiederherstellung der Möglichkeit, über JMP und andere Dienste aufzurufen (Playstore-Version)

fastlane/metadata/android/de-DE/changelogs/42041.txt

@@ -1,5 +0,0 @@
-* Implementierung von Extensible SASL Profile, Bind 2.0 und Fast für schnellere Wiederverbindungen
-* Implementierung von Channel Binding
-* Möglichkeit von einem Audioanruf zu einem Videoanruf zu wechseln
-* Möglichkeit zum Löschen des eigenen Profilbildes hinzugefügt
-* Benachrichtigung für verpasste Anrufe hinzugefügt

fastlane/metadata/android/de-DE/changelogs/42042.txt

@@ -1,2 +0,0 @@
-* Wiederholungsschleife auf Servern beheben, die nur sm:2 unterstützen
-* "Umschalten auf Video" nur anzeigen, wenn die Gegenseite Video unterstützt

fastlane/metadata/android/de-DE/changelogs/42043.txt

@@ -1 +0,0 @@
-* Fehler bei der P2P-Dateiübertragung behoben

fastlane/metadata/android/de-DE/changelogs/42044.txt

@@ -1,3 +0,0 @@
-* Nachrichten werden bei Verwendung von SASL2 nicht mehr erneut gesendet
-* Schwarzes Video zwischen einigen Geräten behoben
-* Absturz bei leeren Passwörtern behoben

fastlane/metadata/android/de-DE/changelogs/42046.txt

@@ -1 +0,0 @@
-* Integration eines UnifiedPush-Verteilers, um Push-Nachrichten für andere UnifiedPush-fähige Apps wie Tusky und Fedilab zu ermöglichen

fastlane/metadata/android/de-DE/changelogs/42047.txt

@@ -1 +0,0 @@
-* Absturz im UnifiedPush-Verteiler behoben

fastlane/metadata/android/de-DE/changelogs/42050.txt

@@ -1 +0,0 @@
-* Vergrößerung des Eckenradius bei Profilbildern

fastlane/metadata/android/de-DE/changelogs/42059.txt

@@ -1,2 +0,0 @@
-* Ziel-SDK wieder auf 33 erhöht
-* Behebt Probleme auf Servern, die SASL2 ohne Inline Stream Management unterstützen

fastlane/metadata/android/de-DE/changelogs/42060.txt

@@ -1 +0,0 @@
-* Fehlerhafte Erkennung von 'q' als kyrillisch behoben

fastlane/metadata/android/de-DE/changelogs/42061.txt

@@ -1 +0,0 @@
-* Channelsuchfunktion aus der Google Play-Version entfernt

fastlane/metadata/android/de-DE/changelogs/42062.txt

@@ -1 +0,0 @@
-* Öffnen von Sicherungsdateien (.ceb) im Dateimanager deaktiviert

fastlane/metadata/android/de-DE/changelogs/42065.txt

@@ -1 +0,0 @@
-* Einführung eines neuen Formats für Sicherungsdateien

fastlane/metadata/android/de-DE/changelogs/42068.txt

@@ -1,2 +0,0 @@
-* Unterstützung der Benachrichtigungseinstellungen pro Unterhaltung
-* Verwendung von Opus für Sprachnachrichten unter Android 10

fastlane/metadata/android/de-DE/changelogs/42072.txt

@@ -1,3 +0,0 @@
-* Änderung der libwebrtc-Abhängigkeit auf M117 und Änderung von libvpx
-* Rückkehr zu AAC für Sprachnachrichten
-* Unterstützung von Spracheinstellungen innerhalb einer App

fastlane/metadata/android/de-DE/changelogs/42074.txt

@@ -1,3 +0,0 @@
-* Unterstützung von Private DNS (DNS über TLS)
-* Unterstützung für designbasiertes Startsymbol
-* Behebt ein seltenes Berechtigungsproblem beim Teilen von Dateien unter Android 11+

fastlane/metadata/android/de-DE/changelogs/4207704.txt

@@ -1,3 +0,0 @@
-* Unterstützung von Private DNS (DNS über TLS)
-* Unterstützung von designbezogenem Startsymbol
-* Behebt ein seltenes Berechtigungsproblem beim Teilen von Dateien unter Android 11+

fastlane/metadata/android/en-US/changelogs/104.txt

@@ -0,0 +1,3 @@
+* Implementation of OTR chats
+* Rebranding from Conversation Clasic to another.im
+* UI improvements and bug fixes

fastlane/metadata/android/en-US/changelogs/204.txt

@@ -0,0 +1,2 @@
+* Fixed message input focus loss
+* Addressed potential crashes caused by NullPointerException

fastlane/metadata/android/en-US/changelogs/42059.txt

@@ -1,2 +1,20 @@
+Upstream:
 * Bump Target SDK to 33 again
 * Fix issues on servers supporting SASL2 w/o inline Stream Management
+* Fix 'q' falsely being recognized as cyrillic
+
+Fork:
+* Implement multi selection for messages
+* Add embedded photo editor
+* Improve replies
+* Prevent vertical scrolling during swipe
+* Separate app id from upstream
+* Disable OMEMO by default
+* Add dialpad
+* Add gateway interaction
+* Add tags navigation
+* Add self contact
+* Don't hide indicator on merged messages
+* Add tags editor
+* Add logs sender
+* Add a menu on long tap on conversations

fastlane/metadata/android/en-US/changelogs/42060.txt

@@ -1 +0,0 @@
-* Fix 'q' falsely being recognized as cyrillic

fastlane/metadata/android/en-US/changelogs/42061.txt

@@ -1 +0,0 @@
-* Remove channel discovery feature from Google Play version

fastlane/metadata/android/en-US/changelogs/42062.txt

@@ -1 +0,0 @@
-* Disable opening backup files (.ceb) from file manager

fastlane/metadata/android/en-US/changelogs/42065.txt

@@ -1 +0,0 @@
-* Introduce new backup file format

fastlane/metadata/android/en-US/changelogs/42068.txt

@@ -1,2 +0,0 @@
-* support per conversation notification settings
-* use opus for voice messages on Android 10

fastlane/metadata/android/en-US/changelogs/42072.txt

@@ -1,3 +0,0 @@
-* Bump libwebrtc dependency to M117 and bump libvpx
-* Go back to AAC for voice messages
-* Support per app language settings

fastlane/metadata/android/en-US/changelogs/4207704.txt

@@ -1,3 +0,0 @@
-* Support Private DNS (DNS over TLS)
-* Support themed launcher icon
-* Fix rare permission issue when sharing files on Android 11+

fastlane/metadata/android/en-US/changelogs/4208104.txt

@@ -1,4 +1,32 @@
+Upstream:
+* Disable opening backup files (.ceb) from file manager
+* Introduce new backup file format
+* support per conversation notification settings
+* Bump libwebrtc dependency to M117 and bump libvpx
+* Support per app language settings
+* Support Private DNS (DNS over TLS)
+* Support themed launcher icon
+* Fix rare permission issue when sharing files on Android 11+
 * Easier access to 'Show QR code'
 * Support PEP Native Bookmarks
 * Add support for SDP Offer / Answer Model (Used by SIP gateways)
 * Raise target API to Android 14
+
+Fork:
+* Fix numerous crashes
+* Add tags for MUC
+* MUC PM in the separate conversation
+* Improve message selection mode title
+* Append author and day for multi select copy value
+* Bump MAM limits
+* Get rid of Soprani.ca bookmark
+* Support primary color picker
+* Group contacts by tag
+* Commands tab in conversation
+* Make replies clickable
+* Fix expandable contact clicks handling
+* Note to self as separate context menu item
+* Fix colors of reply text and conversation swipe background
+* Better messages highlighting
+* Show replies not starting with >
+* Allow to merge private messages

fastlane/metadata/android/en-US/changelogs/4211004.txt

@@ -0,0 +1,31 @@
+The app is renamed to another.im.
+
+* Numerous small fixes
+* Info about PM on MUC details screen
+* Temporary disable domain JID sanity check
+* Support 'Save to downloads' action for attachments
+* Reactions
+* New UI category in expert settings
+* Better self contact handling
+* Split roster by different accounts
+* Group conversation by tags
+* Save expanded items in persistent storage
+* Fix not working accent color
+* Support conversations grouping on ShareWith screen
+* LED color changed to blue
+* Show real reply text instead of fallback
+* New launcher icons
+* Fix multiline reply quote
+* Fix swipe to reply handling
+* Add leakCanary
+* Log reason for SM resume failure
+* Fix notifications fallback color
+* Get rid of command blicks
+* Add checkbox for auto downloading all files when connected to Wi-Fi
+* Improve scroll to bottom button behavior
+* Add notification sound throttling setting, per each contact separately
+* Get rid of upstream bug reports system
+* Add contact JID copy button
+* Move restore backup button from context menu on welcome screen
+* Improve replies on file or image messages
+* Fix reactions handling in case of missing reply stanza

fastlane/metadata/android/en-US/changelogs/4211104.txt

@@ -0,0 +1 @@
+* Fix replies to audio messages

fastlane/metadata/android/en-US/changelogs/4211204.txt

@@ -0,0 +1,2 @@
+* Get rid of outdated kernel version calculation code
+* Fix contact long click crash

fastlane/metadata/android/en-US/changelogs/4211304.txt

@@ -0,0 +1,4 @@
+* Clean code and optimize imports
+* Render reply message author name on the top of replied text
+* Fix conversation position handling while grouping enabled
+* Properly show contact name in MUC

fastlane/metadata/android/en-US/changelogs/4211404.txt

@@ -0,0 +1,13 @@
+* Add Cheogram mention on about screen
+* Fix save to downloads menu item visibility
+* Update Russian and Ukrainian localizations
+* Update caps node field
+* Notifications throttling setting for all conversations
+* Fix gestures handling conflict in commands
+* Support navigation via nav bar
+* Per conversation custom backgrounds
+* Use original file name in chat attachements
+* Support avatars shape customization
+* Medium font for unread conversation title
+* New settings screen
+* Show MUC subject as a pinned message

fastlane/metadata/android/en-US/changelogs/4211504.txt

@@ -0,0 +1,6 @@
+* Added account indicator
+* Group chats are now marked with an additional icon
+* Saved messages now have a brighter background color
+* Added nickname in reply in Multi-User Chats(MUC)
+* Contact status is now displayed separately
+* Updated Russian and Ukrainian localizations

fastlane/metadata/android/en-US/full_description.txt

@@ -0,0 +1,23 @@
+the Another Instant Messenger is not a messenger,
+don't believe the words.
+
+we just offer you a standardized xmpp-client with predicted features which work equally on all platforms.
+in our clients we have realized pure XMPP and you won't step on a hedgehog unexpectedly when you communicate with another xmpp client or server.
+
+because you buy our open-sourced bitcoin,
+we decided to offer you to buy our open-sourced messenger.
+ha-ha joke.
+it's free, really. GPLv3, whatever.
+
+for Android, it's just an improved fork of Conversations,
+
+all necessary XEP's was realized by Conversations devs but we added a cherry on top of this.
+on the server side we are offering free to use Prosody server,
+just connect to [another.im](xmpp:xmppclient-dev@conference.another.im), but we are encouroge you to don't trust us, self-host.
+
+OTR encryption is also supported as 'secret chats' due to otr has been designed for one-time sessions and the concept of 'secret chats' fully corresponds to the idea of the OTR.
+
+also you can just download <a href="https://dev.narayana.im/narayana/anotherim">the source code</a>, compile it and install.
+
+only those who seeks will realize the way to pay us,
+we can offer you additional server-side features and some telecommunication magic on our <a href="https://narayana.im">narayana.im</a>

fastlane/metadata/android/en-US/short_description.txt

@@ -0,0 +1 @@
+Yet Another Conversations fork but...

fastlane/metadata/android/es-ES/changelogs/349.txt

@@ -1,4 +0,0 @@
-* Introducir configuración experta para realizar el descubrimiento de canales en el servidor local en lugar de search.jabber.network
-* Habilitar las marcas de verificación de entrega por defecto y eliminar la configuración
-* Habilitar «Enviar botón indica estado» por defecto y eliminar la configuración
-* Mover los ajustes de copia de seguridad y servicio en primer plano a la pantalla principal

fastlane/metadata/android/es-ES/changelogs/351.txt

@@ -1,3 +0,0 @@
-* Corrección de la transferencia de archivos Jingle IBB
-* Corrección de correcciones repetidas que llenaban la base de datos.
-* Transición a Last Message Correction v1.1

fastlane/metadata/android/es-ES/changelogs/353.txt

@@ -1,4 +0,0 @@
-* Permitir a los usuarios establecer su propio apodo
-* reanudar la descarga de archivos encriptados OMEMO
-* Los canales ahora usan '#' como símbolo en el avatar
-* Quicksy utiliza «siempre» como cifrado OMEMO por defecto (oculta el icono del candado)

fastlane/metadata/android/es-ES/changelogs/360.txt

@@ -1 +0,0 @@
-* Soporte para los parámetros URI de XMPP «?register» y «?register;preauth»

fastlane/metadata/android/es-ES/changelogs/362.txt

@@ -1 +0,0 @@
-* Soporte para el cambio automático de tema en Android 10