narayana/anotherim
narayana/anotherim
3
2
Fork 0
Code Issues 3 Pull requests 1 Actions Packages Projects Releases 6 Wiki Activity

OTR & another.im #23

Merged
Sergei Poljanski merged 65 commits from develop into master 2024-12-09 18:42:00 +00:00
Conversation 0 Commits 65 Files changed 245 +93 -1149
5 changed files with 93 additions and 1149 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit b15b00009f - Show all commits

1210
CHANGELOG.md
View file

File diff suppressed because it is too large Load diff

10
README.md
View file

@ -2,6 +2,12 @@
<p align="center">another.im: the very last word in instant messaging</p> <p align="center">another.im: the very last word in instant messaging</p>
<p align="center"><a href="https://f-droid.org/packages/eu.siacs.conversations.classic">
<img src="https://fdroid.gitlab.io/artwork/badge/get-it-on.png"
alt="Get it on F-Droid"
height="80">
</a></p>
## Design principles ## Design principles
* Be as beautiful and easy to use as possible without sacrificing security or * Be as beautiful and easy to use as possible without sacrificing security or
@ -108,8 +114,8 @@ SCRAM-SHA1, PLAIN, EXTERNAL (client certs) and DIGEST-MD5.
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 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. When trying to connect to OpenFire the bind failure can be a permanent problem when the domain part of the Jabber ID entered in Conversations Classic doesn’t match the domain the OpenFire server feels responsible for. For example OpenFire is configured to use the domain `a.tld` but the Jabber ID entered is `user@b.tld` where `b.tld` also points to the same host. During bind OpenFire tries to reassign the Jabber to `user@a.tld`. Conversations Classic doesn’t like that.
This can be fixed by creating a new account in another.im 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.

6
fastlane/metadata/android/en-US/changelogs/4211504.txt Normal file
View file

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

6
fastlane/metadata/android/ru/changelogs/4211504.txt Normal file
View file

@ -0,0 +1,6 @@
* Добавлен индикатор учетной записи
* Групповые чаты теперь отмечены дополнительным значком
* Закрепленные сообщения теперь имеют более яркий цвет фона
* Добавлен никнейм в ответ в многопользовательских чатах(MUC)
* Статус контакта теперь отображается в отдельно
* Обновлены русская и украинская локализации

6
fastlane/metadata/android/uk/changelogs/4211504.txt Normal file
View file

@ -0,0 +1,6 @@
* Добавлен индикатор учетной записи
* Групповые чаты теперь отмечены дополнительным значком
* Закрепленные сообщения теперь имеют более яркий цвет фона
* Добавлен никнейм в ответ в многопользовательских чатах(MUC)
* Статус контакта теперь отображается в отдельно
* Обновлены русская и украинская локализации