mirror/monocles_chat

Fork 1

mirror of https://codeberg.org/monocles/monocles_chat.git synced 2025-01-15 22:22:22 +01:00

Arne d981d5737b Update Readmes

2024-09-10 08:35:42 +02:00

7.8 KiB

Raw Blame History

Announcement:

Monocles Messenger becomes monocles chat

What you can expect:

Range of functions remains the same
Support chat rooms are merged
Colors and logos are adapted to monocles chat
App is still available for free on codeberg and F-Droid Store

Your monocles Team

monocles chat

🇩🇪… Deutsche Version der Readme hier verfügbar. / Francais ici

monocles chat is a modern and secure Android XMPP client. Based on blabber.im and 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)

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

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 create merge request and add new languages as locales and add and edit translations already existing.

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:

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
Now open a terminal in a directory of you're choice, or navigate to the directory using cd.
Follow steps [6] to [10] of the Windows instructions.
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
```
Follow the remaining steps [12] and [13] of the Windows instructions.

Windows:

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

https://developer.android.com/studio/releases/platform-tools.html
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
Extract the zip-archive (e.g. to C:\ADB\)
Open the command line (CMD) using the start menu: Start > Execute: cmd
Navigate to the directory you extracted the zip to as following. We will be using C:\ADB\
```
c:
cd ADB
```
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.
Inside Developer Options search activate the setting USB-Debugging (sometimes just called Android Debugging).
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.

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

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
```
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
```
Now reproduce the issue encountered.
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

7.8 KiB Raw Blame History