1
0
Fork
You've already forked monocles_chat
0
The monocles chat. A secure chat client based on blabber.im and Conversations for Android with a focus on more privacy but also usability. This chat client is optimized for the monocles server's setting to get more security.
  • Java 98.1%
  • Kotlin 1.5%
  • C++ 0.2%
  • Ruby 0.1%
Find a file
2026年02月25日 11:44:46 +01:00
.builds Further applying monocles database and strings 2024年09月01日 09:54:22 +02:00
.github Disable initial onboarding for now + improve strings 2024年09月14日 15:57:38 +02:00
art Add play store badges 2025年10月28日 18:35:16 +01:00
docs/user Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
fastlane/metadata/android Update changelog + Update translations 2026年02月25日 11:44:46 +01:00
gradle/wrapper Update gradle 2025年08月31日 14:55:44 +02:00
libs bump guava in annotation-processor 2025年03月18日 12:44:16 +01:00
monocleschatFree/debug Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
src Update changelog + Update translations 2026年02月25日 11:44:46 +01:00
.gitignore ignore builds 2024年08月31日 21:50:51 +02:00
.gitlab-ci.yml merge changes from PixArtMessenger 2020年05月07日 21:12:51 +02:00
.woodpecker.yml Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
build.gradle Prepare 2.1.3 2026年02月25日 11:21:37 +01:00
CHANGELOG.md Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
Gemfile Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
Gemfile.lock Initial rebase for monocles chat 1.8 2024年08月31日 20:41:31 +02:00
gradle.properties increase RAM for build 2025年07月12日 09:23:58 +02:00
gradlew Update gradle 2025年08月31日 14:55:44 +02:00
gradlew.bat Update gradle 2025年08月31日 14:55:44 +02:00
LICENSE added license file 2014年03月25日 01:47:08 +01:00
monocles_chat.doap Mark XEP-0424 as complete 2026年01月25日 12:04:17 +01:00
proguard-rules.pro Fix up proguard rules 2025年04月26日 22:19:56 +02:00
README-de.md Update README-de.md 2026年02月20日 13:41:02 +01:00
README-fr.md docs: clean trailing whitespaces from READMEs 2026年02月14日 10:34:32 +01:00
README-it.md docs: clean trailing whitespaces from READMEs 2026年02月14日 10:34:32 +01:00
README-pl.md docs: clean trailing whitespaces from READMEs 2026年02月14日 10:34:32 +01:00
README-tr.md docs: clean trailing whitespaces from READMEs 2026年02月14日 10:34:32 +01:00
README.md Update README.md 2026年02月20日 13:40:16 +01:00
settings.gradle Merge branch 'master' of https://codeberg.org/iNPUTmice/Conversations 2024年09月10日 08:14:55 +02:00

monocles chat

🇩🇪... Deutsche Version der Readme hier verfügbar. / Francais ici / Italiano qui / Przeczytaj po polsku / Türkçe sürüm burada

monocles chat is a modern and secure Android XMPP client. Based on Conversations but with a lot of changes and additional features. The changes aim to improve usability and ease transition from pre-installed and other widespread chats. Here are some screenshots:

Screens designed by Pigeonalley (https://pigeonalley.com)

Download

Now on F-Droid Now on Google Play

Presettings

monocles chat has different presettings compared to blabber.im:

  • don't show previews of weblinks in chat
  • don't show previews of locations in chat
  • don't automatically download all attachments

OTR

monocles chat supports OTR encryption! Though it's not easy to use OTR does have some advantages: https://en.wikipedia.org/wiki/Off-the-Record_Messaging#Implementation

Download

monocles chat is available for install in the F-Droid Alternatively beta-release APKs are available via codeberg: Releases

monocles chat nightly and beta

nightly or beta-release APKs are available via codeberg: Releases

Social Media

Follow us on monocles social

There are also English and German speaking XMPP-room focusing on support and development of the monocles chat.

If you are interested in the development of the chat, here is a MUC for you (English and German speaking):

Development-Chat: development@conference.monocles.de

There also is an Support-MUC where you can ask questions and get help with issues you may encounter, see further below for details.

How can I support translations ?

You can improve or create translations on Codeberg Translate. Thank you very much.

Help! I've encountered issues!

The easiest way to get some help is to join our support-MUC (both English and German).

Support-Chat invite link: support@conference.monocles.de

If we can't fix your problem there, you can open an issue here, detailing your problem, how to reproduce it and provide logs. See instructions below on how to create log files.

How to create debug logs? (adb)

GNU/Linux, OSX and other Unix-like systems:

  1. First install The Android Debugging Bridge, if not already present.

    Debian and derivates like Ubuntu / Linux Mint
    sudo apt-get update
    sudo apt-get update adb
    # Debian Jessie or older:
    # sudo apt-get install android-tools-adb
    
    openSUSE 42.2 and 42.3
    sudo zypper ref
    sudo zypper install android-tools
    
    openSUSE Tumbleweed

    here you need to add the following repo (e.g. via Yast): http://download.opensuse.org/repositories/hardware/openSUSE_Tumbleweed/

    alternatively you have the option to use the 1 Click installer https://software.opensuse.org/package/android-tools

    other systems

    install adb using a method appropriate for your system

  2. Now open a terminal in a directory of you're choice, or navigate to the directory using cd.

  3. Follow steps [6] to [10] of the Windows instructions.

  4. Start outputting your log to a file on your computer. We will be using logcat.txt. Enter:

    $ adb -d logcat -v time | grep -i "monocles chat" > logcat.txt
    
  5. Follow the remaining steps [12] and [13] of the Windows instructions.

Windows:

  1. Download Google's SDK-platform tools for your operating system:

    https://developer.android.com/studio/releases/platform-tools.html

  2. In case they were not included: You also need the ADB_drivers for your version of Microsoft Windows:

    https://developer.android.com/studio/run/win-usb.html

  3. Extract the zip-archive (e.g. to C:\ADB\)

  4. Open the command line (CMD) using the start menu: Start > Execute: cmd

  5. Navigate to the directory you extracted the zip to as following. We will be using C:\ADB\

    c:
    cd ADB
    
  6. On your smartphone open the settings and search for the item Developer Options. If this option is not already present on your phone you will need to unlock it beforehand. To do this navigate to Settings > About phone, there locate Build number (or similar) and tap it 7-times in succession. You should now see a notification, that you are now a developer. Congrats, Developer Options are now available in your settings menu.

  7. Inside Developer Options search activate the setting USB-Debugging (sometimes just called Android Debugging).

  8. Connect your phone to your computer via USB cable. The necessary drivers should now be downloaded and installed if not already present. On Windows all necessary drivers should be downloaded automatically if you followed step [2] beforehand. On most GNU/Linux systems no additional action is required.

  9. If everything worked out, you can now return to the command line and test if your device is being recognised. Enter adb devices -l; you should see output similar to:

    > adb devices -l
    List of devices attached
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    042111560169500303f4 unauthorized
    
  10. If your devices is labelled as unautorized, you must first accept a prompt on your phone asking if debugging over USB should be allowed. When rerunning adb devices you should now see:

    > adb devices
    List of devices attached
    042111560169500303f4 device
    
  11. Start outputting your log to a file on your computer. We will be using logcat.txt in C:\ADB\. Just enter the following (without > into the command line):

    > adb -d logcat -v time | FINDSTR monocles_chat > logcat.txt
    
  12. Now reproduce the issue encountered.

  13. Stop logging (Ctrl+C). Now take a close look at your log file and remove any personal and private information you may find before sending it together with a detailed description of your issue, instructions on how to reproduce to me. You can use GitHub's issue tracker: Issues