From: Ryan Prior <ryanprior@hey.com>
To: aviva <aviva@gmx.us>,
Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>,
Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>
Subject: Re: updating Jami to "Together", Qt update?
Date: Wed, 18 Nov 2020 20:17:54 +0000 [thread overview]
Message-ID: <23c326627f4668f3fc63d84296a6ebfe1ea594a5@hey.com> (raw)
In-Reply-To: <87zh3ebhkp.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On November 18, 2020, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> aviva <aviva@gmx.us> writes:
>
> > nobody i know uses it. without a community of users, it has no
> purpose
>
> There must always be a first user ;)
I use Jami regularly with a few adventurous friends who like peer-to-
peer things. We often have to fall back to another video system like
Jitsi to finish our calls, but keep returning for more punishment
because we believe in the dream.
I have been specifically burned before by the Jami package in Guix. It
hasn't played well with other Jami software; I started having better
luck when I switched to using the Debian package. But if you get the
Together release working well I'm absolutely down to give it another
shot!
[-- Attachment #2: Type: text/html, Size: 3081 bytes --]
next prev parent reply other threads:[~2020-11-18 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 1:45 updating Jami to "Together", Qt update? Jan Wielkiewicz
2020-11-18 2:06 ` aviva
2020-11-18 18:11 ` Jan Wielkiewicz
2020-11-18 19:04 ` aviva
2020-11-18 19:17 ` Pierre Neidhardt
2020-11-18 20:17 ` Ryan Prior [this message]
2020-11-18 23:16 ` Jan Wielkiewicz
2020-11-19 6:08 ` aviva
2020-11-18 8:10 ` Pierre Neidhardt
2020-11-18 18:15 ` Jan Wielkiewicz
2020-12-07 23:03 ` Marius Bakke
2020-12-08 21:14 ` Jan Wielkiewicz
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=23c326627f4668f3fc63d84296a6ebfe1ea594a5@hey.com \
--to=ryanprior@hey.com \
--cc=aviva@gmx.us \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).