savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-08-28T03:07:55Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/856Backup and or restore doesn't work at all2022-08-28T03:07:55ZBackup and or restore doesn't work at allMiui 11 android 10 this is fdroid, but it was the problem on GP too
A long time ago i reported an issue that convinced me i have made a mistake or typo in password entering. https://git.jami.net/savoirfairelinux/ring-client-android/issu...Miui 11 android 10 this is fdroid, but it was the problem on GP too
A long time ago i reported an issue that convinced me i have made a mistake or typo in password entering. https://git.jami.net/savoirfairelinux/ring-client-android/issues/836
Reproduced it with backuping on jami app with success
making an app clone or jami-2
entering backup from file with right password
it lies that that account doesn't exist, even if that account is online and if offline
the reason i didn't try to believe device wasn't compromised or that i didn't make a typo is that i would never think that a gnu stabile project could have this kind of bug. But i gave it a chance multiple times, and i guess its closely connected with jami-android-backup-button as i remember, i may be wrong
!![Screenshot_2020-12-12-10-09-07-973_cx.ring](/uploads/a8f7f7cdeb1c15a661c691bbc714ad6f/Screenshot_2020-12-12-10-09-07-973_cx.ring.jpg)![Screenshot_2020-12-12-10-09-19-470_cx.ring](/uploads/4b592172015a074e8940a03a97508838/Screenshot_2020-12-12-10-09-19-470_cx.ring.jpg)![Screenshot_2020-12-12-10-09-33-778_com.google.android.documentsui](/uploads/bde1612d55883ed1f24a534d038d72fa/Screenshot_2020-12-12-10-09-33-778_com.google.android.documentsui.jpg)![Screenshot_2020-12-12-10-10-08-061_com.miui.securitycore](/uploads/9818cad231fc62310b76bfbeaa602ec4/Screenshot_2020-12-12-10-10-08-061_com.miui.securitycore.jpg)![Screenshot_2020-12-12-10-10-13-364_com.miui.securitycore](/uploads/5f4c5cbb94e8d0c4120f067a3fef26f7/Screenshot_2020-12-12-10-10-13-364_com.miui.securitycore.jpg)![Screenshot_2020-12-12-10-11-05-344_com.miui.home](/uploads/e9ba6aae102a1a4183701bdb932dc893/Screenshot_2020-12-12-10-11-05-344_com.miui.home.jpg)![Screenshot_2020-12-12-10-11-14-851_cx.ring](/uploads/ef005acfa5c7510fbd8b14ea37a49cde/Screenshot_2020-12-12-10-11-14-851_cx.ring.jpg)![Screenshot_2020-12-12-10-11-30-062_me.zhanghai.android.files](/uploads/017e006e136c1d51fdee66e6cdcd9e1a/Screenshot_2020-12-12-10-11-30-062_me.zhanghai.android.files.jpg)![Screenshot_2020-12-12-10-11-52-353_cx.ring](/uploads/62f91e74d7d54289f2207b80848248d7/Screenshot_2020-12-12-10-11-52-353_cx.ring.jpg)![Screenshot_2020-12-12-10-11-55-012_cx.ring](/uploads/d66b7fb7d75f4497ffbf8a3e98357970/Screenshot_2020-12-12-10-11-55-012_cx.ring.jpg)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/214Jams settings: show linked device2020-12-16T18:00:12ZSébastien BlinJams settings: show linked deviceAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1120Add/Remove video media stream to/from an ongoing call2020-12-29T22:50:16ZMohamed ChibaniAdd/Remove video media stream to/from an ongoing callCurrently, if a call is established with only audio media, the only way to add video media to the call is to hang-up and start with a new audio/video call.
This feature will allow a user to upgrade an ongoing audio-only call to audio+vid...Currently, if a call is established with only audio media, the only way to add video media to the call is to hang-up and start with a new audio/video call.
This feature will allow a user to upgrade an ongoing audio-only call to audio+video call.Iteration 25Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/213Chat does not accept copy-paste from mouse middle button (linux)2022-01-07T21:27:16ZAlbert Babí OllerChat does not accept copy-paste from mouse middle button (linux)The linux copy-paste functionality with the mouse middle button does not work on the chat. However, "Ctrl+C" - "middle-button" works fine.The linux copy-paste functionality with the mouse middle button does not work on the chat. However, "Ctrl+C" - "middle-button" works fine.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/212Call back button is inaccessible for some conference layouts2021-11-19T21:39:58ZAlbert Babí OllerCall back button is inaccessible for some conference layoutsParticipant overlay is on top of call-view overlay, so for some layouts the button cannot be clicked.
![image](/uploads/f8b46bcb7a1d1fc77bde9c1e5135a011/image.png)Participant overlay is on top of call-view overlay, so for some layouts the button cannot be clicked.
![image](/uploads/f8b46bcb7a1d1fc77bde9c1e5135a011/image.png)Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/211Fullscreen call always takes the same screen2020-12-15T08:21:53ZAlbert Babí OllerFullscreen call always takes the same screenWhen working with multiple screens, calls are always "full-screened" on the same.When working with multiple screens, calls are always "full-screened" on the same.Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/210Conversation switch during a call does not show the correct messages2020-12-22T14:37:28ZAlbert Babí OllerConversation switch during a call does not show the correct messagesSwitching between a call and another conversation only loads the correct messages the first time.Switching between a call and another conversation only loads the correct messages the first time.Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/451swarm chat2021-06-12T11:39:24ZKateryna Kostiukswarm chatDONE:
- load conversations
- add conversation
- send messages
- load messages
- receive message
- accept conversation
- start conversation with first interaction (send message/file/place call)
- sort interactions by time
- confi...DONE:
- load conversations
- add conversation
- send messages
- load messages
- receive message
- accept conversation
- start conversation with first interaction (send message/file/place call)
- sort interactions by time
- configure call interactions
- configure data transfer interactions
- configure contact interactions
- remove interaction
- remove conversation
TODO:
- save last read interaction
CHANGES ON CLIENT SIDE:
- use string for interaction id instead of int
- connect and handle signal newInteractionsAvailable(accountId, conversationId)
- implement lazy loading (may be not for first version)Swarm-chatKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1228Webcam is not detected on raspberry2023-05-26T13:59:17ZFlowWebcam is not detected on raspberryHello,
The webcam isn't detected on raspberry 3 with camera module.
I tried multiple version:
- 20190215 from raspbian repo
- 20201208.3 from jami repo
- 20201027.1 from snap
I doesn't see any specific error in the log.
```
** Message: ...Hello,
The webcam isn't detected on raspberry 3 with camera module.
I tried multiple version:
- 20190215 from raspbian repo
- 20201208.3 from jami repo
- 20201027.1 from snap
I doesn't see any specific error in the log.
```
** Message: 15:23:31.124: Jami GNOME client version: 9bada8a43cf9fec860da2b2b2d2fc8d242220e33
** Message: 15:23:31.124: git ref: unknown
No migration required
Can't open file: "/home/pi/.local/share/jami/fba3beaba81aae3/profile.vcf"
(jami-gnome:2209): libnotify-WARNING **: 15:23:33.009: Failed to connect to proxy
(jami-gnome:2209): Gtk-WARNING **: 15:23:33.013: Child name 'calls' not found in GtkStack
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:34.933: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
** (jami-gnome:2209): WARNING **: 15:23:35.357: no primary network connection detected, check network settings
(jami-gnome:2209): Gdk-CRITICAL **: 15:23:35.873: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:2209): Gtk-WARNING **: 15:23:40.832: Theme parsing error: <data>:1:79: Not using units is deprecated. Assuming 'px'.
could not open shm area "" , shm_open failed: Argument invalide
```
Thanks for your helphttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1119Importing an unencrypted account archive suggests entering a password2023-03-28T12:43:27ZMaxim CournoyerImporting an unencrypted account archive suggests entering a passwordThe UI (of at least the desktop and Android clients) suggest entering a password when importing an account archive, even when such archive was not password protected.
I suggest that the account be imported "sur le champ", without furthe...The UI (of at least the desktop and Android clients) suggest entering a password when importing an account archive, even when such archive was not password protected.
I suggest that the account be imported "sur le champ", without further confusion when Jami (automatically) detects the account archive is not encrypted (password protected).https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/209Distribution 'void' not supported.2020-12-24T18:57:20ZFabio KrapohlDistribution 'void' not supported.I wanted to follow the build instructions, but already the first step (./make-ring.py --init) didn't work, because void linux is not supported.
Why do you have specific install rules for every system instead of just using some default ru...I wanted to follow the build instructions, but already the first step (./make-ring.py --init) didn't work, because void linux is not supported.
Why do you have specific install rules for every system instead of just using some default rules, and maybe add some special cases, where necessary, like basically every other project does?
You could just use some fallback, which uses the most common stuff.
I could also try to add some void installadion method myself, but I'm not sure, where to start.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/371Shoud use device URI instead of account URI for conferenceInfo2022-01-24T16:46:04ZPierre LespagnolShoud use device URI instead of account URI for conferenceInfoPrevent conflicts when using same account with separate devices.Prevent conflicts when using same account with separate devices.Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/208Problem with maximize/minimize button for the host2020-12-16T18:05:14ZPierre LespagnolProblem with maximize/minimize button for the hostFor the host we have
- Maximize only for layout 1
- Maximize only for layout 2
we should have:
- Maximize and minimize for layout 1
- Minimize only for layout 2For the host we have
- Maximize only for layout 1
- Maximize only for layout 2
we should have:
- Maximize and minimize for layout 1
- Minimize only for layout 2Albert Babí OllerPierre LespagnolAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/207Delete the black border on the layout overlay2020-12-16T18:05:02ZPierre LespagnolDelete the black border on the layout overlayAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/206Problem to switch on the remaining call after conference for the host2020-12-16T18:04:53ZPierre LespagnolProblem to switch on the remaining call after conference for the hostSometimes, the remaining call is not selected after the end of a conference.Sometimes, the remaining call is not selected after the end of a conference.Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/370The host is unmute when he creates a conference2021-01-19T17:31:41ZPierre LespagnolThe host is unmute when he creates a conferenceThe mute information for the host is not keptThe mute information for the host is not keptPierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/369Swarm: Christmas edition - beta build2021-01-04T20:00:06ZSébastien BlinSwarm: Christmas edition - beta buildIteration 25Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/205Hyperlink in dark theme is unreadable2020-12-24T19:12:14ZlinsuiHyperlink in dark theme is unreadable![sshot-028](/uploads/e4dc7c6eaf14331e91974727420edf92/sshot-028.png)![sshot-028](/uploads/e4dc7c6eaf14331e91974727420edf92/sshot-028.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1118ring-daemon does not compile from Gentoo ebuild2020-12-09T20:46:41ZRickring-daemon does not compile from Gentoo ebuildI have been attempting to compile Jami from a Gentoo overlay (ring-overlay).
Unfortunately, ring-daemon fails to compile. The error message, from the net-voip/ring-daemon-99999999 ebuild, is:
curl -sS -f -L --retry-delay 10 --retry 4 -...I have been attempting to compile Jami from a Gentoo overlay (ring-overlay).
Unfortunately, ring-daemon fails to compile. The error message, from the net-voip/ring-daemon-99999999 ebuild, is:
curl -sS -f -L --retry-delay 10 --retry 4 -- "https://github.com/P-H-C/phc-winner-argon2/archive/1eea0104e7cb2a38c617cf90ffa46ce5db6aceda.tar.gz" > "../../contrib/tarballs/argon2-1eea0104e7cb2a38c617cf90ffa46ce5db6aceda.tar.gz"
curl: (6) Couldn't resolve host 'github.com'
In a Gentoo forum at https://forums.gentoo.org/viewtopic-t-1110414-highlight-jami.html The issue is diagnosed by user Hu as completely reasonable:
"Is this failure when curl is run from inside the ebuild? If so, this failure is expected and correct. To support reproducible builds, ebuilds run in a network sandbox, without the ability to download arbitrary blobs directly from the Internet. The ebuild should direct Portage to download the relevant files as part of SRC_URI, then use the copy from the files directory."
The ebuild needs to be corrected before any compilation is possiblehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1117Feature Idea: HTTP tunneling through Jami, for social IoT, remote tech suppor...2023-09-18T19:31:34ZDaniel DunnFeature Idea: HTTP tunneling through Jami, for social IoT, remote tech support, and profile pagesPersonal websites, in my opinion, were the defining element that really made the early web great. Sadly, they have almost been driven to nonexistence by social media, which on many sites does not truly allow any level of expression beyo...Personal websites, in my opinion, were the defining element that really made the early web great. Sadly, they have almost been driven to nonexistence by social media, which on many sites does not truly allow any level of expression beyond a news feed.
## Use Cases
Current IoT devices can often have some kind of social aspect, such as sharing fitness data, and at the very least usually need some way to access them remotely, which is currently almost exclusively the domain of centralized services.
Many times, one also wants to give control of a local service to a remote user, for tech support purposes as in TeamViewer, and quite often one wants to share a file with a group on a "Pull" basis, rather than directly sending to one person.
In cases of censorship, or off-grid scenarios where only one person has real internet access, one might also want to share access to a public internet resource, to a few specific users only.
Applications like Kiwix that serve offline copies of things like Wikipedia could provide trusted educational content over an entire mesh network.
The system could be used for remote access to NextCloud and similar.
More... Ahem... Personal devices are apparently becoming cloud IoT enabled, and there was just a big controversy or something in the news, and I would imagine that's one area
where you would really want to control exactly who has access.
Profile pages with images are a staple of social media, and are especially useful if you make a dedicated account for a certain project.
A secure and decentralized association between a server and your account allows you to integrate seamlessly with other decentralized projects, some of which could eventually have deeper integration, without Jami needing to specifically support them.
Similar to images and locations, any arbitrary dynamic content could be shared with other users in a chat, like live webcam views, or perhaps even embedded directly inline into a chat window in an iframe.
## Implementation
One possibility that would seem to cover all of these use cases with minimal overhead is HTTP tunneling. Jami could expose an unlimited number of HTTP/WebSocket services per account, each with a freely assignable name.
These services would then be available via Jami acting as a proxy, on any other device, at SERVICENAME.USERID.localhost:someport. As completely separate subdomains, all sandboxing and security is provided by the browser.
SERVICENAME is never sent or advertised in the cleartext at any point, and the UI for creating tunnels defaults to a long random name, making them equivalent to capability URLs unless changed to short public URLs purposefully.
An API is added via DBus or Android Intents, to allow other apps to easily specify the tunnel they want to create.
Services can have expiration dates on them, so that you do not forget to delete one you only meant to share briefly. Expired services are completely deleted if not refreshed, preventing any risk of reusing a capability URL that you meant to only share for one session.
### Profile Pages
One could define the empty service name(Just USERID.localhost) as a public profile page, with a 32KB limit or such, that syncs across accounts and caches on other nodes on a most-recent-wins basis. Maybe you could even store it directly in the DHT, digitally signed.
Any additional content or images could then be loaded using the proxy mechanism on a home server, failing gracefully to just this minimal DHT-only content.
## Prior Art
Similar proposal in XMPP: https://xmpp.org/extensions/xep-0332.html
Data forms in XMPP cover similar use cases: https://xmpp.org/extensions/xep-0004.html
Now abandoned Mozilla proposal for IoT on LAN: https://wiki.mozilla.org/FlyWeb
Nabu Casa seems to use the same embedded key in subdomain concept as this, albeit
on a centralized remote server, to access Home Assistant via the cloud: https://www.nabucasa.com/config/remote/
## Security Issues
### IP-revealing Privacy issue for profile pages and inline chat content
Profile pages could use tracking pixels and the like, breaking I2P et al. But we are proxying everything through localhost, and so we can use the content-security-policy to stop this.
This does not stop WebRTC exfiltration from leaking your IP, but the entire profile can be wrapped in an iframe that disables JS entirely, and inline chat content can be hidden behind a "Do you want to load this content? It may include resources from an external server" popup.
For anything but profile pages, any privacy issues are going to be up to the user, as with any other site.
Ideally profiles would be served in an embedded WebView anyway, giving another place to further enforce no-js behavior.