From: Denver Gingerich <denver@ossguy.com>
To: Msavoritias <marinus.savoritias@disroot.org>
Cc: Adonay Felipe Nogueira <adfeno@hyperbola.info>,
libreplanet-discuss@libreplanet.org
Subject: Re: Matrix communication protocol.
Date: Thu, 30 Jul 2020 04:37:25 +0000 [thread overview]
Message-ID: <20200730043725.GC25289@ossguy.com> (raw)
In-Reply-To: <1596039936.1150.2@disroot.org>
On Wed, Jul 29, 2020 at 06:25:36PM +0200, Msavoritias wrote:
> On Fri, Jul 24, 2020 at 11:47, Adonay Felipe Nogueira via
> libreplanet-discuss <libreplanet-discuss@libreplanet.org> wrote:
>
> Note: I don't speak for FSF, nor for GNU. Em 23/07/2020 18:56,
> Msavoritias escreveu:
>
> I would like to ask is it in the works to have an official FSF/GNU
> server in the future? Are there any blockers I can help with?
>
> FSF already has XMPP service for their associate members.
>
> I guess it comes down to personal preference but for me I didn't see
> the same features in all the clients I tried and almost all of them
> were badly designed. This doesn't help with convincing people to use
> XMPP.
Where did you go to determine which XMPP clients to try? And which clients did you try?
I believe there should be better resources to allow people to more easily find the best XMPP clients - I'm trying to do my part with the recommendations at https://jmp.chat/#clients (for the free software service I run). In short, use Gajim or Conversations. If you want fancy design but less features, then Dino.
Hopefully we can make these recommendations more widely-known so that people don't give up on XMPP. It's an excellent protocol and is very easy to use and featureful if you have the right client.
Denver
https://jmp.chat/
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2020-07-30 18:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 21:56 Matrix communication protocol Msavoritias
[not found] ` <87eep1bw5k.fsf@gmail.com>
2020-07-24 8:37 ` Msavoritias
2020-07-25 7:07 ` Adrien Bourmault (neox on Freenode)
2020-07-24 14:47 ` Adonay Felipe Nogueira via libreplanet-discuss
2020-07-29 16:25 ` Msavoritias
2020-07-30 4:37 ` Denver Gingerich [this message]
2020-07-30 16:04 ` Msavoritias
2020-07-30 16:21 ` Ali Reza Hayati
2020-07-30 19:30 ` Msavoritias
2020-07-30 16:27 ` Denver Gingerich
2020-07-30 19:51 ` Msavoritias
2020-07-31 3:00 ` Denver Gingerich
2020-07-31 8:58 ` Msavoritias
2020-07-31 9:12 ` Adrien Bourmault (neox on Freenode)
2020-07-31 19:20 ` Adrien Bourmault (neox on freenode)
2020-08-04 13:43 ` Adonay Felipe Nogueira via libreplanet-discuss
2020-08-04 21:03 ` Msavoritias
2020-08-01 17:25 ` Msavoritias
2020-08-01 17:34 ` Denver Gingerich
2020-08-01 23:01 ` Adrien Bourmault (neox on Freenode)
2020-08-03 17:07 ` Jean Louis
2020-08-04 7:09 ` Adrien Bourmault (neox on Freenode)
2020-08-04 20:41 ` Msavoritias
2020-08-03 21:45 ` Msavoritias
2020-08-04 7:08 ` Adrien Bourmault (neox on Freenode)
2020-08-04 20:52 ` Msavoritias
2020-08-01 23:35 ` Msavoritias
2020-08-04 13:07 ` Adonay Felipe Nogueira via libreplanet-discuss
2020-08-04 13:16 ` Adonay Felipe Nogueira via libreplanet-discuss
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200730043725.GC25289@ossguy.com \
--to=denver@ossguy.com \
--cc=adfeno@hyperbola.info \
--cc=libreplanet-discuss@libreplanet.org \
--cc=marinus.savoritias@disroot.org \
/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).