Compare commits

...

48 commits

Author SHA1 Message Date
kosyak e9659f0fa3 fix disappearing bookmarks (issue #12) 2024-08-18 14:03:49 +02:00
kosyak ce40742ddf bump to 2.3.1 2024-08-12 10:30:07 +02:00
kosyak 5034778a7d get rid of jcenter 2024-08-12 10:19:51 +02:00
kosyak 3d5ecaf376 fix crash on group chats screen 2024-08-12 10:19:31 +02:00
kosyak a124b7e790 fix broken replies on conversation reopen 2024-08-06 20:12:05 +02:00
Bohdan Horbeshko 9f3fe75342 update fastlane metadata && bump version code (#5)
Reviewed-on: #5
Reviewed-by: kosyak <kosyak@narayana.im>
Co-authored-by: Bohdan Horbeshko <bodqhrohro@gmail.com>
Co-committed-by: Bohdan Horbeshko <bodqhrohro@gmail.com>
2024-08-06 18:03:50 +00:00
Sergei Poljanski 37aa0160b6 fdroid/build (#6)
Fix gradle warns for F-Droid  issues bot

Reviewed-on: #6
Reviewed-by: kosyak <kosyak@narayana.im>
Co-authored-by: Sergei Poljanski <me@asxp.io>
Co-committed-by: Sergei Poljanski <me@asxp.io>
2024-08-06 18:03:27 +00:00
Sergei Poljanski 1301f43eba lang/ru (#7)
Russian translation from Codeberg

Reviewed-on: #7
Reviewed-by: kosyak <kosyak@narayana.im>
Co-authored-by: Sergei Poljanski <me@asxp.io>
Co-committed-by: Sergei Poljanski <me@asxp.io>
2024-08-06 18:02:46 +00:00
Sergei Poljanski 66f56c25d6 Merge pull request 'eliminate hardcoded applicationId' (#8) from appid-hardcode-fix into master
Reviewed-on: #8
Reviewed-by: kosyak <kosyak@narayana.im>
2024-08-06 18:01:52 +00:00
Sergei Poljanski 689386fda6 Merge pull request 'hruuu' (#9) from hruuu into master
Reviewed-on: #9
Reviewed-by: kosyak <kosyak@narayana.im>
2024-08-06 18:01:07 +00:00
Bohdan Horbeshko 229bd9133b hruuu 2024-08-06 18:01:07 +00:00
Sergei Poljanski 4d52ee060d Merge pull request 'readme' (#11) from readme into master
Reviewed-on: #11
Reviewed-by: kosyak <kosyak@narayana.im>
2024-08-06 18:00:21 +00:00
Sergei Poljanski 3763829da0
about 2024-08-06 20:37:47 +03:00
Sergei Poljanski 97073a6b1e
updated readme 2024-08-06 18:41:50 +03:00
kosyak 4c2dd3e933 pinned message brighter background color 2024-08-06 09:37:53 +02:00
Bohdan Horbeshko 87bf8aa138 eliminate hardcoded applicationId 2024-08-06 06:55:36 +03:00
kosyak cfdaaec86e better ellipsize for subject text 2024-08-05 23:38:07 +02:00
kosyak 869182d640 add nick into reply fallback only for MUC 2024-08-05 23:28:54 +02:00
kosyak d7d922c1d1 account indicator near conversations 2024-08-05 23:18:55 +02:00
kosyak 9892ff8d77 better replies fallback 2024-08-05 22:54:41 +02:00
kosyak 42d59adc78 show only contacts in contacts tab 2024-08-05 22:38:51 +02:00
kosyak cf9d0c4f09 show contact status in a separate widget 2024-08-05 22:34:10 +02:00
kosyak f709e32805 mark group chats with additional icon 2024-08-05 21:20:22 +02:00
kosyak 2b2ecbb44e fix wired 'Hide offline' behavior 2024-08-05 21:19:52 +02:00
kosyak 1fa72c42a0 bump to 2.3.0 2024-07-28 09:21:51 -04:00
kosyak 07bef730aa muc imporvements 2024-07-28 09:20:35 -04:00
kosyak e94aae746d new settings screen 2024-07-21 13:49:31 +02:00
kosyak 14c3df535d medium font for unread conversation title 2024-07-21 12:29:15 +02:00
kosyak 21658d20d0 support avatars shape customization 2024-07-21 12:00:17 +02:00
kosyak 7ef0e53892 use original file name in chat attachements 2024-07-14 18:05:34 +02:00
kosyak 481f5ebfc1 per conversation custom backgrounds 2024-07-14 17:01:50 +02:00
kosyak 4453ad71ac support navigation via nav bar 2024-07-14 15:01:05 +02:00
kosyak c145a6b8e5 Revert "OTR implementation"
This reverts commit 900c72ed98.
2024-07-14 12:23:22 +02:00
kosyak 61af01ff28 Revert "otr fixes"
This reverts commit a136138daa.
2024-07-14 12:23:01 +02:00
kosyak 516f6321ef Merge branch 'master' of https://dev.narayana.im/narayana/Conversations 2024-07-14 12:22:41 +02:00
kosyak a136138daa otr fixes 2024-07-14 12:22:02 +02:00
kosyak 900c72ed98 OTR implementation 2024-07-07 23:23:47 +02:00
kosyak e3a4d0f36e Merge pull request 'hruu' (#3) from hruu into master
Reviewed-on: #3
Reviewed-by: kosyak <kosyak@narayana.im>
2024-06-22 07:05:04 +00:00
Bohdan Horbeshko af32590eaf hruu 2024-06-18 02:53:05 +03:00
kosyak 3d5794ea72 fix gestures handling conflict in commands 2024-06-17 11:17:02 +02:00
Sergei Poljanski f27240a611 Merge pull request 'hru' (#2) from hru into master
Reviewed-on: narayana/Conversations-Classic#2
Reviewed-by: kosyak <kosyak@narayana.im>
2024-06-17 07:27:59 +00:00
Sergei Poljanski 629838f27c Merge pull request 'ru lang' (#1) from lang/ru into master
Reviewed-on: narayana/Conversations-Classic#1
Reviewed-by: kosyak <kosyak@narayana.im>
2024-06-16 23:50:45 +00:00
Bohdan Horbeshko 126b826522 hru 2024-06-17 01:41:05 +03:00
kosyak ece06b9651 notifications throttling setting for all conversations 2024-06-16 23:52:38 +02:00
kosyak 9f0b59af9f update caps node field 2024-06-16 22:54:02 +02:00
Sergei Poljanski a5e45ca995
ru lang 2024-06-16 19:37:59 +03:00
kosyak 25cd65e4e7 fix save to downloads menu item visibility 2024-06-05 22:40:34 +01:00
kosyak d037e940c7 add cheogram mention on about screen 2024-06-05 22:38:32 +01:00
733 changed files with 3363 additions and 5919 deletions

View file

@ -28,14 +28,15 @@
### XMPP Features ### XMPP Features
Conversations works with every XMPP server out there. However XMPP is an Conversations Classic works with every XMPP server out there. However XMPP is an
extensible protocol. These extensions are standardized as well in so called extensible protocol. These extensions are standardized as well in so called
XEP's. Conversations supports a couple of these to make the overall user XEP's. Conversations Classic supports a couple of these to make the overall user
experience better. There is a chance that your current XMPP server does not experience better. There is a chance that your current XMPP server does not
support these extensions; therefore to get the most out of Conversations you support these extensions; therefore to get the most out of Conversations Classic you
should consider either switching to an XMPP server that does or — even better — 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: 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 * [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). 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. * [XEP-0163: Personal Eventing Protocol](http://xmpp.org/extensions/xep-0163.html) for avatars and OMEMO.
@ -44,14 +45,14 @@ 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 * [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. 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-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 * [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 your desktop client and thus allows you to switch seamlessly from your mobile
client to your desktop client and back within one conversation. 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-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
offline.
* [XEP-0352: Client State Indication](http://xmpp.org/extensions/xep-0352.html) lets the server know whether or not * [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 Conversations is in the background. Allows the server to save bandwidth by
withholding unimportant packages. withholding unimportant packages.
@ -66,14 +67,10 @@ run your own XMPP server for you and your friends. These XEP's are:
#### How do I install Conversations? #### How do I install Conversations?
Conversations is entirely open source and licensed under GPLv3. So if you are a Conversations Classic is entirely open source and licensed under GPLv3. So if you are a
software developer you can check out the sources from GitHub and use Gradle to software developer you can check out the sources from GitHub and use Gradle to
build your apk file. build your apk file.
#### I don't have a Google Account but I would still like to make a donation
Im 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? #### 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 dont 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. 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 dont like to use *conversations.im* use a web search engine of your choice to find another provider. Or maybe your university has one. Or you can run your own. Or ask a friend to run one. Once you've found one, you can use Conversations to create an account. Just select *register new account* on server within the create account dialog.
@ -88,12 +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. 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 #### Where can I set up a custom hostname / port
Conversations will automatically look up the SRV records for your domain name Conversations Classic will automatically look up the SRV records for your domain name
which can point to any hostname port combination. If your server doesnt provide which can point to any hostname port combination. If your server doesnt provide
those please contact your admin and have them read those please contact your admin and have them read
[this](http://prosody.im/doc/dns#srv_records). If your server operator is unwilling [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 to fix this you can enable advanced server settings in the expert settings of
Conversations. Conversations Classic.
#### I get 'Incompatible Server' #### I get 'Incompatible Server'
@ -104,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). 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 On rare occasions this error message might also be caused by a server not providing
a login (SASL) mechanism that Conversations is able to handle. Conversations supports a login (SASL) mechanism that Conversations Classic is able to handle. Conversations Classic supports
SCRAM-SHA1, PLAIN, EXTERNAL (client certs) and DIGEST-MD5. SCRAM-SHA1, PLAIN, EXTERNAL (client certs) and DIGEST-MD5.
#### I get 'Bind failure'. What does that mean? #### I get 'Bind failure'. What does that mean?
Some Bind failures are transient and resolve themselves after a reconnect. 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 doesnt 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 doesnt like that. 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 doesnt 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 doesnt like that.
This can be fixed by creating a new account in Conversations that uses the Jabber ID `user@a.tld`. This can be fixed by creating a new account in Conversations Classic that uses the Jabber ID `user@a.tld`.
Note: This is kind of a weird quirk in OpenFire. Most other servers would just throw a 'Server not responsible for domain' error instead of attempting to reassign the Jabber ID. Note: This is kind of a weird quirk in OpenFire. Most other servers would just throw a 'Server not responsible for domain' error instead of attempting to reassign the Jabber ID.
@ -122,16 +119,10 @@ Maybe you attempted to use the Jabber ID `test@b.tld` because `a.tld` doesnt
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). 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.**
#### Im getting this annoying permanent notification ##### Android &lt;= 7.1 or Conversations Classic from F-Droid (all Android versions)
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 wont have the problem of a *forced* foreground notification if you are getting your app from F-Droid.) 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.
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 ##### 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. Long press the permanent notification and disable that particular type of notification by moving the slider to the left. This will make the notification disappear but create another notification (this time created by the operating system itself.) that will complain about Conversations (and other apps) using battery. Starting with Android 8.1 you can disable that notification again with the same method described above.
@ -139,39 +130,24 @@ Long press the permanent notification and disable that particular type of notifi
##### Android 9.0+ ##### 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. 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 *Googles 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 doesnt 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 doesnt 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 dont 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 doesnt 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. Thats 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 doesnt work for me. Where can I get help? #### Conversations doesnt 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). 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 A lot of people in there are able to answer basic questions about the usage of
Conversations or can provide you with tips on running your own XMPP server. If Conversations Classic or can provide you with tips on running your own XMPP server. If
you found a bug or your app crashes please read the Developer / Report Bugs you found a bug or your app crashes please read the Developer / Report Bugs
section of this document. section of this document.
#### How does the address book integration work? #### How does the address book integration work?
The address book integration was designed to protect your privacy. Conversations The address book integration was designed to protect your privacy. Conversations Classic
neither uploads contacts from your address book to your server nor fills your 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 address book with unnecessary contacts from your online roster. If you manually
add a Jabber ID to your phones address book Conversations will use the name and add a Jabber ID to your phones address book Conversations Classic will use the name and
the profile picture of this contact. To make the process of adding Jabber IDs to 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 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 details within Conversations Classic. This will start an "add to address book" intent
with the JID as the payload. This doesn't require Conversations to have write with the JID as the payload. This doesn't require Conversations Classic to have write
permissions on your address book but also doesn't require you to copy/paste a permissions on your address book but also doesn't require you to copy/paste a
JID from one app to another. JID from one app to another.
@ -227,23 +203,23 @@ changeable on the fly. Metrics like last active client (the client which sent
the last message) are much better. the last message) are much better.
Unfortunately these modern replacements for legacy XMPP features are not widely Unfortunately these modern replacements for legacy XMPP features are not widely
adopted. However Conversations should be an instant messenger for the future and adopted. However Conversations Classic should be an instant messenger for the future and
instead of making Conversations compatible with the past we should work on instead of making Conversations Classic compatible with the past we should work on
implementing new, improved technologies and getting them into other XMPP clients implementing new, improved technologies and getting them into other XMPP clients
as well. as well.
Making these status and priority optional isn't a solution either because Making these status and priority optional isn't a solution either because
Conversations is trying to get rid of old behaviours and set an example for Conversations Classic is trying to get rid of old behaviours and set an example for
other clients. other clients.
#### How do I backup / move Conversations to a new device? #### How do I backup / move Conversations Classic to a new device?
Use the Backup button in the Settings. Use the Backup button in the Settings.
#### Conversations is missing a certain feature #### Conversations Classic is missing a certain feature
Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`](xmpp:xmppclient-dev@conference.narayana.im)
### Security ### Security
@ -255,7 +231,7 @@ Please report it to our XMPP conference [`xmppclient-dev@conference.narayana.im`
#### How do I use OpenPGP #### How do I use OpenPGP
Before you continue reading you should note that the OpenPGP support in Before you continue reading you should note that the OpenPGP support in
Conversations is experimental. This is not because it will make the app unstable Conversations Classic is experimental. This is not because it will make the app unstable
but because the fundamental concepts of PGP aren't ready for widespread use. 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. 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 So in theory your contact list should consist of Public-Key-IDs instead of
@ -293,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). 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 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. sure that you have every participant's public key in your OpenKeychain.
Right now there is no check in Conversations to ensure that. Right now there is no check in Conversations Classic to ensure that.
You have to take care of that yourself. Go to the conference details and 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 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 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 very small conferences with contacts you are already using OpenPGP with. This
feature is regarded experimental. Conversations is the only client that uses feature is regarded experimental. Conversations Classic is the only client that uses
XEP-0027 with conferences. (The XEP neither specifically allows nor disallows XEP-0027 with conferences. (The XEP neither specifically allows nor disallows
this.) this.)

View file

@ -18,20 +18,12 @@ apply plugin: 'org.jetbrains.kotlin.android'
repositories { repositories {
google() google()
mavenCentral() mavenCentral()
jcenter()
maven { url='https://jitpack.io'} maven { url='https://jitpack.io'}
} }
configurations { configurations {
playstoreImplementation
freeImplementation freeImplementation
conversationsFreeImplementation conversationsFreeImplementation
conversationsPlaystorImplementation
conversationsPlaystoreImplementation
quicksyPlaystoreImplementation
quicksyPlaystoreImplementation
quicksyFreeImplementation
quicksyImplementation
} }
dependencies { dependencies {
@ -39,13 +31,6 @@ dependencies {
implementation 'androidx.viewpager:viewpager:1.0.0' 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.open-keychain.open-keychain:openpgp-api:v5.7.1'
implementation("com.github.CanHub:Android-Image-Cropper:2.2.0") implementation("com.github.CanHub:Android-Image-Cropper:2.2.0")
implementation 'androidx.appcompat:appcompat:1.6.1' implementation 'androidx.appcompat:appcompat:1.6.1'
@ -64,7 +49,6 @@ dependencies {
implementation 'de.measite.minidns:minidns-hla:0.2.4' implementation 'de.measite.minidns:minidns-hla:0.2.4'
implementation 'me.leolin:ShortcutBadger:1.1.22@aar' implementation 'me.leolin:ShortcutBadger:1.1.22@aar'
implementation 'org.whispersystems:signal-protocol-java:2.6.2' implementation 'org.whispersystems:signal-protocol-java:2.6.2'
implementation 'com.makeramen:roundedimageview:2.3.0'
implementation "com.wefika:flowlayout:0.4.1" implementation "com.wefika:flowlayout:0.4.1"
//noinspection GradleDependency //noinspection GradleDependency
implementation('com.github.natario1:Transcoder:v0.9.1') { implementation('com.github.natario1:Transcoder:v0.9.1') {
@ -91,7 +75,8 @@ dependencies {
implementation 'androidx.constraintlayout:constraintlayout:2.1.4' implementation 'androidx.constraintlayout:constraintlayout:2.1.4'
implementation "androidx.recyclerview:recyclerview:1.2.1" implementation "androidx.recyclerview:recyclerview:1.2.1"
implementation 'com.github.bumptech.glide:glide:4.15.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.github.chrisbanes:PhotoView:2.3.0'
//implementation 'com.splitwise:tokenautocomplete:3.0.2' //implementation 'com.splitwise:tokenautocomplete:3.0.2'
@ -117,8 +102,8 @@ android {
defaultConfig { defaultConfig {
minSdkVersion 24 minSdkVersion 24
targetSdkVersion 34 targetSdkVersion 34
versionCode 42113 versionCode 42115
versionName "2.2.4" versionName "2.3.1"
archivesBaseName += "-$versionName" archivesBaseName += "-$versionName"
applicationId "eu.siacs.conversations.classic" applicationId "eu.siacs.conversations.classic"
resValue "string", "applicationId", applicationId resValue "string", "applicationId", applicationId
@ -155,58 +140,22 @@ android {
flavorDimensions += "distribution" flavorDimensions += "distribution"
productFlavors { 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 { conversations {
dimension "mode" dimension "mode"
} }
playstore {
dimension "distribution"
versionNameSuffix "+playstore"
}
free { free {
dimension "distribution" dimension "distribution"
versionNameSuffix "+free" //versionNameSuffix "+free"
} }
} }
sourceSets { sourceSets {
quicksyFree {
java {
srcDir 'src/quicksyFree/java'
}
}
quicksyPlaystore {
java {
srcDir 'src/quicksyPlaystore/java'
}
res {
srcDir 'src/quicksyPlaystore/res'
}
}
conversationsFree { conversationsFree {
java { java {
srcDir 'src/conversationsFree/java' srcDir 'src/conversationsFree/java'
} }
} }
conversationsPlaystore {
java {
srcDir 'src/conversationsPlaystore/java'
}
res {
srcDir 'src/conversationsPlaystore/res'
}
}
} }
buildTypes { buildTypes {

View file

@ -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

View file

@ -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

View file

@ -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)

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

@ -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)

View file

@ -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)

View file

@ -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

View file

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

View file

@ -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

View file

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

View file

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

View file

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

View file

@ -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

View file

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

View file

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

View file

@ -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

View file

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

View file

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

View file

@ -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

View file

@ -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)

View file

@ -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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

@ -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

View file

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

View file

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

View file

@ -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

View file

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

View file

@ -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

View file

@ -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

View file

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

View file

@ -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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

@ -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

View file

@ -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+

View file

@ -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+

View file

@ -1,2 +1,20 @@
Upstream:
* Bump Target SDK to 33 again * Bump Target SDK to 33 again
* Fix issues on servers supporting SASL2 w/o inline Stream Management * 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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

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

View file

@ -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' * Easier access to 'Show QR code'
* Support PEP Native Bookmarks * Support PEP Native Bookmarks
* Add support for SDP Offer / Answer Model (Used by SIP gateways) * Add support for SDP Offer / Answer Model (Used by SIP gateways)
* Raise target API to Android 14 * 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

View file

@ -0,0 +1,31 @@
The app is renamed to Conversations Classic.
* 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

View file

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

View file

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

View file

@ -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

View file

@ -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

View file

@ -9,31 +9,34 @@ Design principles:
Features: Features:
* End-to-end encryption with either <a href="http://conversations.im/omemo/">OMEMO</a> or <a href="http://openpgp.org/about/">OpenPGP</a> * End-to-end encryption with either <a href="https://en.wikipedia.org/wiki/OMEMO">OMEMO</a> or <a href="http://openpgp.org/about/">OpenPGP</a>
* Sending and receiving images * Sending and receiving images
* Encrypted audio and video calls (DTLS-SRTP) * Encrypted audio and video calls (DTLS-SRTP) with DTMF dialpad
* Intuitive UI that follows Android Design guidelines * Intuitive UI that follows Android Design guidelines
* Pictures / Avatars for your Contacts * Pictures / Avatars for your Contacts
* Syncs with desktop client * Syncs with desktop client
* Conferences (with support for bookmarks) * Conferences (with support for bookmarks)
* Address book integration * Address book integration
* Multiple accounts / unified inbox * Multiple accounts / unified inbox
* Builtin image editor
* Very low impact on battery life * Very low impact on battery life
Conversations makes it very easy to create an account on the free conversations.im server. However Conversations will work with any other XMPP server as well. A lot of XMPP servers are run by volunteers and are free of charge.
XMPP Features: XMPP Features:
Conversations works with every XMPP server out there. However XMPP is an extensible protocol. These extensions are standardized as well in so called XEPs. Conversations 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 you should consider either switching to an XMPP server that does or - even better - run your own XMPP server for you and your friends. Conversations Classic works with every XMPP server out there. However XMPP is an extensible protocol. These extensions are standardized as well in so called XEPs. 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.
These XEPs are - as of now: These XEPs are - as of now:
* XEP-0050: Ad-Hoc Commands lets to interact with gateways.
* XEP-0065: SOCKS5 Bytestreams (or mod_proxy65). Will be used to transfer files if both parties are behind a firewall (NAT). * XEP-0065: SOCKS5 Bytestreams (or mod_proxy65). Will be used to transfer files if both parties are behind a firewall (NAT).
* XEP-0163: Personal Eventing Protocol for avatars * XEP-0163: Personal Eventing Protocol for avatars.
* XEP-0191: Blocking command lets you blacklist spammers or block contacts without removing them from your roster. * XEP-0191: Blocking command lets you blacklist spammers or block contacts without removing them from your roster.
* XEP-0198: Stream Management allows XMPP to survive small network outages and changes of the underlying TCP connection. * XEP-0198: Stream Management allows XMPP to survive small network outages and changes of the underlying TCP connection.
* XEP-0215: External Service Discovery will be used to discover STUN and TURN servers which facilitate P2P A/V calls.
* 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-0280: Message Carbons which automatically syncs the messages you send to your desktop client and thus allows you to switch seamlessly from your mobile client to your desktop client and back within one conversation.
* XEP-0237: Roster Versioning mainly to save bandwidth on poor mobile connections * XEP-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 was offline. * 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 is in the background. Allows the server to save bandwidth by withholding unimportant packages. * 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-0363: HTTP File Upload allows you to share files in conferences and with offline contacts. Requires an additional component on your server. * 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.

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 525 KiB

After

Width:  |  Height:  |  Size: 64 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 449 KiB

After

Width:  |  Height:  |  Size: 93 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 612 KiB

After

Width:  |  Height:  |  Size: 109 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 475 KiB

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 339 KiB

After

Width:  |  Height:  |  Size: 83 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 364 KiB

After

Width:  |  Height:  |  Size: 227 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 284 KiB

After

Width:  |  Height:  |  Size: 107 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 168 KiB

After

Width:  |  Height:  |  Size: 99 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 418 KiB

After

Width:  |  Height:  |  Size: 66 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 106 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 433 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 424 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 462 KiB

View file

@ -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

View file

@ -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

View file

@ -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)

View file

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

View file

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

View file

@ -1,2 +0,0 @@
* Proporcionar vista previa de PDF en Android 5+
* Utilizar IVs de 12 bytes para OMEMO

View file

@ -1,2 +0,0 @@
* Corregir la selección de avatar en algunos dispositivos Android 10
* Corregir la transferencia de archivos más grandes

View file

@ -1 +0,0 @@
* Llamadas de audio/vídeo (requiere soporte de servidor en forma de servidores STUN y TURN detectables mediante XEP-0215)

View file

@ -1,2 +0,0 @@
* Respuesta audible (marcación, llamada iniciada, llamada finalizada) para llamadas de voz.
* Solucionado el problema de reintento de videollamada fallida

View file

@ -1,2 +0,0 @@
* Añadir botón para cambiar de cámara durante la videollamada
* Corregidas las llamadas de voz en tablets

View file

@ -1,3 +0,0 @@
* Mover el icono de llamada a la izquierda para mantener otros iconos de la barra de herramientas en un lugar coherente.
* Mostrar la duración de la llamada durante las llamadas de audio
* Desempate en las llamadas A/V (dos personas que se llaman al mismo tiempo)

View file

@ -1,2 +0,0 @@
* Reestructuración de la interfaz de inicio de sesión con certificado
* Añadir la posibilidad de anclar chats en la parte superior (añadir a favoritos)

Some files were not shown because too many files have changed in this diff Show more