unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Gottfried <gottfried@posteo.de>,  help-guix@gnu.org
Subject: Re: substitute for Skype
Date: Tue, 02 Aug 2022 11:15:52 -0400	[thread overview]
Message-ID: <87o7x21xsn.fsf@gmail.com> (raw)
In-Reply-To: <vi5oax3-6YK11fKCfU-mR1C_DLWJigMJNIvbGkGLGLCkaWdKbz4B5-oDHZaFZBkulkZ72h6mRvNTTVi3HbFqmcG9ntibUznKapSMeU086kg=@protonmail.com> (Luis Felipe's message of "Mon, 01 Aug 2022 19:18:50 +0000")

Hi Luis,

Luis Felipe <luis.felipe.la@protonmail.com> writes:

> Hi Gottfried,
>
> On Monday, August 1st, 2022 at 15:47, Gottfried <gottfried@posteo.de> wrote:
>
>> Has somebody got experience with Jami or Mumble?
>
> I've used Jami until recently. As other people already mentioned, installing the "jami" package should be enough.
>
> I only used it to converse with one person at a time, not group [audio|video]chats. When it worked, it was enjoyable. Unfortunately, most of the time it didn't.
>
> I tried it for several months at different times, checking if upgrades
> would improve the experience, but the experience wasn't good enough to
> grow a list of contacts that included people from mainstream culture
> (people used to WhatsApp and proprietary software in general). The few
> contacts I had (~5) eventually stopped using the application because
> of its constant malfunctioning. Some contacts left making harsh
> comments about it.
>
> Most noticeable problems:
>
> • Missing messages
> • Sharing images, voice messages and files seldom worked

Sadly, I can relate.  Luckily there is some hope.  The new swarm
mechanism for syncing conversations via libgit is maturing and promises
to avoid the loss of messages when delivery can't happen in real time
(such as when the remote participant is offline).  I think the latest
release we have packaged already implements it in 1:1 conversations.

Mobile clients may have other issues (the need to use push notifications
or a gateway server to the distributed network to avoid wasting the tiny
battery in a few hours introduces its own share of complications -- and
bugs).

Thanks for having shared your experience!

Maxim


  reply	other threads:[~2022-08-02 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 11:00 substitute for Skype Gottfried
2022-08-01 11:50 ` (
2022-08-01 11:55 ` Akib Azmain Turja
2022-08-01 12:13   ` (
2022-08-01 12:36     ` Maxim Cournoyer
2022-08-01 15:26       ` Gottfried
2022-08-01 15:39         ` (
2022-08-01 15:47         ` Gottfried
2022-08-01 15:49           ` (
2022-08-01 19:18           ` Luis Felipe
2022-08-02 15:15             ` Maxim Cournoyer [this message]
2022-08-01 15:50         ` Maxim Cournoyer
2022-08-02  7:48         ` David Lecompte
2022-08-02 11:55           ` Benjamin Slade
2022-08-02 13:00             ` Akib Azmain Turja
2022-08-02 19:22               ` Csepp
2022-08-04  0:03                 ` Gary Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7x21xsn.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).