unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: email@msavoritias.me
Cc: 68894@debbugs.gnu.org
Subject: bug#68894: Prosody guix service required fixes.
Date: Sat, 03 Feb 2024 11:31:41 +0100	[thread overview]
Message-ID: <87zfwhon3m.fsf@lassieur.org> (raw)
In-Reply-To: <aaf2e500-26a5-e8e0-1aab-b97441d23080@fannys.me> (email@msavoritias.me's message of "Sat, 3 Feb 2024 09:56:56 +0200")

On Sat, Feb 03 2024, email@msavoritias.me wrote:

> We could simplify it by a lot i think either way. Some ways could be: 
>
> 1. Remove the opaque-configuration since it never worked for raw
> content which does already.
>
> 2. Remove the ssl config section here
> https://guix.gnu.org/en/manual/devel/en/guix.html#index-ssl
>
> nobody should be touching these settings either way.
>
> Personally I would prefer to have a scheme config but could go either
> way. I use xmpp as my only-full time messaging and own the xmpp guix
> room.
>
> This prosody service is going to be used for joinjabber which you can
> see here btw https://codeberg.org/joinjabber/Infra
>
> I also have talked about a guix self hosted xmpp server for a guix
> room so prosody would be used for that.
>
> My thinking is that yeah the xmpp support in guix is not great and
> should be better. To that end in the short term I would be interested
> in updating/maintaining/adding xmpp software/services to guix.
>
> Longer term as i wrote maybe also putting all xmpp stuff in a single
> file. but that can come later 😄 An xmpp team would also be something
> that could be done at some point.

This all sounds good.  I'm glad the service is used and I'll help you or
review if you need!

Cheers
Clément




      reply	other threads:[~2024-02-03 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 15:46 bug#68894: Prosody guix service required fixes email
2024-02-02 16:59 ` Clément Lassieur
2024-02-03  7:56   ` email
2024-02-03 10:31     ` Clément Lassieur [this message]

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=87zfwhon3m.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=68894@debbugs.gnu.org \
    --cc=email@msavoritias.me \
    /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).