savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2020-12-22T20:02:52Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/800[Group-chat] Avoid sha1 in git signatures2020-12-22T20:02:52ZSébastien Blin[Group-chat] Avoid sha1 in git signaturesSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/64update doc with trusted CA organizations2021-01-06T19:31:27ZGuillaume Hellerupdate doc with trusted CA organizationsAdd:
* list of trusted CA organizations that can deliver SSL certificate files (let's encrypt, godaddy, etc)
* add example on how to generate free certificates via let's encrypt (should replace the existing part on how to request certi...Add:
* list of trusted CA organizations that can deliver SSL certificate files (let's encrypt, godaddy, etc)
* add example on how to generate free certificates via let's encrypt (should replace the existing part on how to request certificates using openssl)Larbi GharibLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/65Add relative path for cert.pem and privkey.pem on server start2021-01-08T20:58:29ZLarbi GharibAdd relative path for cert.pem and privkey.pem on server startLarbi GharibLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/719Protect application (and data) via password2021-01-21T11:01:26ZJami BotProtect application (and data) via passwordIssue generated from Tuleap's migration script.
**Originally submitted by: Andreas Jahnke (ladon83)**
Currently when the application (Ring-gnome) starts, you are automatically logged in.
This seems to be a security risk as anybody wit...Issue generated from Tuleap's migration script.
**Originally submitted by: Andreas Jahnke (ladon83)**
Currently when the application (Ring-gnome) starts, you are automatically logged in.
This seems to be a security risk as anybody with access to the computer has also access to private messages.
Only workaround:
Unlink the account before closing.
However this is not usable in the real world.
It would be great to block the access via a password.
Whenever starting the application, a password should be needed (this can be optional of course).
EDIT:
This issue include:
+ Encrypting histories on the device
+ Encrypting the confighttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1171[Feature request] Choose definition and quality before sending pictures2021-01-22T10:12:09ZChristophe Laurent[Feature request] Choose definition and quality before sending picturesSometimes it is not necessary to send à large definition and max quality pic, could be interetsing to choose before sending it.Sometimes it is not necessary to send à large definition and max quality pic, could be interetsing to choose before sending it.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/383Checking for working udev doesn't work.2021-01-23T19:32:14ZFuchtelJockelChecking for working udev doesn't work.This doesn't catch the nonfunctional udev installation that flatpaks ship with.
```cpp
udev_ = udev_new();
if (!udev_)
goto udev_failed;
udev_mon_ = udev_monitor_new_from_netlink(udev_, "udev");
if (!udev_mon_)
...This doesn't catch the nonfunctional udev installation that flatpaks ship with.
```cpp
udev_ = udev_new();
if (!udev_)
goto udev_failed;
udev_mon_ = udev_monitor_new_from_netlink(udev_, "udev");
if (!udev_mon_)
goto udev_failed;
if (udev_monitor_filter_add_match_subsystem_devtype(udev_mon_, "video4linux", NULL))
goto udev_failed;
/* Enumerate existing devices */
devenum = udev_enumerate_new(udev_);
if (devenum == NULL)
goto udev_failed;
if (udev_enumerate_add_match_subsystem(devenum, "video4linux")) {
udev_enumerate_unref(devenum);
goto udev_failed;
}
```
Currently the flatpak version works using a patch but maybe this could be added as a build option or some of the checks are broken?
```
diff --git a/src/media/video/v4l2/video_device_monitor_impl.cpp b/src/media/video/v4l2/video_device_monitor_impl.cpp
index c6a4a2e9f..faa8f4179 100644
--- a/src/media/video/v4l2/video_device_monitor_impl.cpp
+++ b/src/media/video/v4l2/video_device_monitor_impl.cpp
@@ -126,7 +126,9 @@ VideoDeviceMonitorImpl::VideoDeviceMonitorImpl(VideoDeviceMonitor* monitor)
udev_enumerate_unref(devenum);
goto udev_failed;
}
-
+
+ goto udev_failed;
+
udev_monitor_enable_receiving(udev_mon_);
/* Note that we enumerate _after_ monitoring is enabled so that we do not
* loose device events occuring while we are enumerating. We could still
```https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/46Communication between IPv6-only to IPv4-only networks2021-01-31T21:27:09ZSébastien BlinCommunication between IPv6-only to IPv4-only networksTo perform that, we need to have a ipv6<->ipv4 mechanism somewhere. Because the first peer is only able to listen on ipv6 addresses and the second one on ipv4 addresses, something between those peers need to do that job.
And the good ne...To perform that, we need to have a ipv6<->ipv4 mechanism somewhere. Because the first peer is only able to listen on ipv6 addresses and the second one on ipv4 addresses, something between those peers need to do that job.
And the good news is that TURN is here for that and this behavior is described by [RFC6156](https://tools.ietf.org/html/rfc6156).
So, for coturn, the config needs two relay-addr entries. One for ipv6, one for ipv4 (cf https://github.com/coturn/coturn/issues/154). This is ok for turn.jami.net, so nothing to do there.
For Jami, this needs to be handled by pjproject but this is not the case for now:
https://github.com/pjsip/pjproject/commit/4b6835c9b818eb8a434d35beccd5faa1b684533b
This needs to be able to set "IPV4_AF_TYPE" for PJ_STUN_ATTR_REQ_ADDR_TYPE to be able to allocate an IPv4 candidate for an IPv6 address. However, the rest is not supported because the session will fail. So, the code needs to be done.
Depends on: https://github.com/pjsip/pjproject/issues/2520Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/301No relay (Turn) candidate in SDP with IOS when being connected in LTE/4G2021-02-17T16:19:15ZCyrille BéraudNo relay (Turn) candidate in SDP with IOS when being connected in LTE/4GSee attached file for log (with an Android comparison)[sdpios-andoid.log](/uploads/891e408417fd3059abed50184563f396/sdpios-andoid.log)
To reproduce:
Be connected on LTE/4G, make a call.
btw, why all the addresses are twice as candidate?See attached file for log (with an Android comparison)[sdpios-andoid.log](/uploads/891e408417fd3059abed50184563f396/sdpios-andoid.log)
To reproduce:
Be connected on LTE/4G, make a call.
btw, why all the addresses are twice as candidate?BacklogMohamed ChibaniKateryna KostiukSébastien BlinMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/119Please, write clear release notes at the AppStore2021-02-22T16:17:44ZArtemy GavrelyukPlease, write clear release notes at the AppStoreHello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a ...Hello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a new version of Jami at AppStorehttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/67Expired session will editing2021-02-24T17:40:41ZLarbi GharibExpired session will editingStart new session
Start editing
After few minutes user experiences issuesStart new session
Start editing
After few minutes user experiences issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1204Feature request: Improve blocking function and add anti-spam mechanism2021-03-07T11:43:53Ztid liFeature request: Improve blocking function and add anti-spam mechanismChinese user, Android side, currently using version 20210226-01 on F-Droid.
Maybe I don't know how to use it well, I found some problems and didn't find a solution by myself. Here are some questions and suggestions. Hope it can help to ...Chinese user, Android side, currently using version 20210226-01 on F-Droid.
Maybe I don't know how to use it well, I found some problems and didn't find a solution by myself. Here are some questions and suggestions. Hope it can help to improve Jami
Questions
1. About the blocking function
First, the contacts still appear in the conversation list after blocking. Second, when testing, if a stranger wants to add me, the logic of this blocking feature is surprising - to block, you have to become a contact before blocking, if you delete the contact, then the blocking is useless. Third, the blocking list can not delete contacts. If you want to remove a contact from it, you can only choose to add each other. Fourth, blocking will also appear in other cases of invalid.
Reproduce some cases of the above: When account A clicks the block button on the request when account B adds it, account B will appear directly in the conversation list and Jami show that it has been added as a contact. The other invalidation is that once Account A has initiated the message, the chat between the two parties is unobstructed after that.
The strange logic of the above blocking function baffles me.
2. About contact requests
As far as I know, Jami doesn't seem to have any mechanism to block spam contact requests locally. As long as you know the account ID, you can add them. Every time an account is added, the account receives a contact request, and due to the strange logic of the blocking feature, these contacts will fill up the conversation list if you choose to block them.
3. About other features
First, when switching between multiple accounts on the account details page, there may be a situation where the small avatar does not correspond to the large avatar below, or even all the content does not correspond (still the content of the account before switching). Secondly, if I don't give Jami permission to take photos when I show the QR code on the account details page, Jami will be stuck there, and the button in the top right corner will keep blinking. I don't think it's necessary to get permission when I show the QR code.
Suggestions
1. About blocking function and blocking list
I hope to add a switch to control whether to show the blocked people in the conversation list. And the contacts in blocking list can be unblocked. Because if there are no two sides added, it is not necessary to add each other after unblocking a stranger.
2. About contact request
I hope to add an optional verification function when adding contacts, such as questions, etc. TOX's mechanism can also be referred to. And it would be nice to allow accounts to be set up so that they can only add other contact but can not be added. But most importantly, whatever spam prevention mechanism is used, I hope that requests for accounts that do not pass verification can be set to not show.
Thanks a lot for reading my tedious statement, I hope it will help to improve Jami.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/898Feature request first start prompt for disabling battery optimizations2021-03-08T11:26:32ZFeature request first start prompt for disabling battery optimizationsIt is a system's prompt for "Special app access >> Disable battery optimizations" . I know that "p≡p | Pretty Easy Privacy (pEp)" app requests it on first start, and that "Whatsapp" uses that feature too.It is a system's prompt for "Special app access >> Disable battery optimizations" . I know that "p≡p | Pretty Easy Privacy (pEp)" app requests it on first start, and that "Whatsapp" uses that feature too.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/902Send image/videos form gallery - AndroidTV2021-03-08T18:59:39ZAmirhossein NaghshzanSend image/videos form gallery - AndroidTVCurrently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.Currently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/476No SIP registration due to bad network detection2021-03-15T14:53:10ZEnrico ScholzNo SIP registration due to bad network detectionjami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
*...jami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
```
<details>
<summary>Full Log</summary>
<pre>
$ ring.cx --debug
(jami-gnome:822803): GLib-DEBUG: 14:24:25.931: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:822803): DEBUG: 14:24:25.931: debug enabled
** Message: 14:24:25.933: Jami GNOME client version: development
** Message: 14:24:25.933: git ref: unknown
** (jami-gnome:822803): DEBUG: 14:24:25.933: enabling autostart
** (jami-gnome:822803): DEBUG: 14:24:25.933: checking /usr/share/jami-gnome/jami-gnome.desktop
(jami-gnome:822803): dconf-DEBUG: 14:24:25.933: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** (jami-gnome:822803): DEBUG: 14:24:25.934: '/home/ensc/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:822803): dbind-WARNING **: 14:24:25.945: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de_DE
(jami-gnome:822803): GLib-GIO-DEBUG: 14:24:26.106: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): GLib-DEBUG: 14:24:26.178: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Connecting to session manager
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
Can't open file: "/home/ensc/.local/share/jami/606bab6fe62f6e4c/profile.vcf"
** (jami-gnome:822803): DEBUG: 14:24:26.254: notify server name: naughty, vendor: awesome, version: 3.5, spec: 1.0
(jami-gnome:822803): Gtk-WARNING **: 14:24:26.255: Child name 'calls' not found in GtkStack
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.257: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GoaVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (g-dbus-error-quark, 3)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.413: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.414: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.565: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.585: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_notify: /net/jami/JamiGnome/show-main-window
(process:822825): GLib-GIO-DEBUG: 14:24:26.661: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: NetworkManager not running
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: _g_io_module_get_default: Found default implementation netlink (GNetworkMonitorNetlink) for ?gio-network-monitor?
(WebKitWebProcess:822824): dbind-WARNING **: 14:24:26.672: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
(jami-gnome:822803): dconf-DEBUG: 14:24:26.701: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
** (jami-gnome:822803): WARNING **: 14:24:26.718: no primary network connection detected, check network settings
(process:822825): GLib-GIO-DEBUG: 14:24:26.740: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-height
(WebKitWebProcess:822824): GLib-GIO-DEBUG: 14:24:26.796: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): Gdk-CRITICAL **: 14:24:26.880: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-height
</pre>
</details>
I am not using Gnome and network is managed manually (no NetworkManager)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/907MIUI/Android's dark theme inverts my qr code image2021-03-15T17:55:08ZMIUI/Android's dark theme inverts my qr code imageWhen system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account...When system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account" tab,
2. in qr section there are qr image and "Share my QR" button,
3. in "conversations" tab in "About jami" the "credits" button background,
4. In account choosing menu, default profile pictures (only the "human" part), and in profile picture choosing dialog. The human part changes its color to black, while in chats those stay white
(Button backgrounds in 1, 2, 3 are white in jami's dark theme, and android's dark mode turns them to very dark color. But button text is still kind of readable because of blueish text color)
MIUI 12.0.1 Android 10https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/126SIP account: could not detect audio only call2021-03-17T20:10:56ZKateryna KostiukSIP account: could not detect audio only callA video preview is showing for an incoming audio-only callA video preview is showing for an incoming audio-only callhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/70Replace Statement database management with ORM such as Hibernate2021-03-17T20:17:11ZLarbi GharibReplace Statement database management with ORM such as HibernateAdrien BéraudGuillaume HellerLarbi GharibAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/905Feature request screen overlay detector2021-03-18T01:49:46ZFeature request screen overlay detectorScreenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Br...Screenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Briar" has developed this feature, and it doesn't let you enter passwords or chat until you figure out how to stop some of listed apps that have permission.https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/17SDK: add dependsOn to preference structure2021-03-19T16:09:21ZAline Gondim SantosSDK: add dependsOn to preference structure"dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic."dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/463Replace Portaudio with WASAPI to support communication device enumeration and...2021-03-22T19:50:52ZAndreas TraczykReplace Portaudio with WASAPI to support communication device enumeration and output loopbackAndreas TraczykAndreas Traczyk