unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ada Stevenson <adanskana@gmail.com>
To: MSavoritias <email@msavoritias.me>,
	Vivien Kraus <vivien@planete-kraus.eu>,
	Felix Lechner <felix.lechner@lease-up.com>,
	guix-devel@gnu.org
Subject: Re: RFI: Guix XMPP service.
Date: Mon, 11 Dec 2023 06:53:09 +0000	[thread overview]
Message-ID: <db2ea64b-7b12-f3ef-c69c-4e637197da45@gmail.com> (raw)
In-Reply-To: <68dcc944-6388-fb83-998a-be9568c11864@fannys.me>

Hi,

On 12/10/23 4:04 PM, MSavoritias wrote:
>
> On 12/10/23 17:56, Vivien Kraus wrote:
>> Le dimanche 10 décembre 2023 à 17:45 +0200, MSavoritias a écrit :
>>>> There is also a trust issue. For acceptance, we need bridging. For
>>>> bridging, we need policing. And for policing, we need people with
>>>> time.

I am of the opinion that bridging would be a bad idea. The differences 
between IRC and XMPP are significant enough that bringing would probably 
be more disruptive than conducive to acceptance. A better approach would 
to simply have a separate IRC and XMPP channel. If people end up 
preferring XMPP, more people will simply elect to use it. In any project 
eventually the main communication channels tend to split up into smaller 
groups once they get to a certain size anyway for a number of reasons. 
This doesn't stop these other spaces from being 'accepted', and if we 
have the XMPP channel become official, I think this is acceptance enough.


>>> That's a good question yeah. Whether we want bridging that is.
>>> Personally I am leaning that we don't.
>>>
>>> Because bridging can ruin the experience of people that use XMPP. But
>>> I
>>> can see it either way.
>> Maybe we could do something a little smarter, like having sneek deliver
>> messages in both IRC and XMPP.
>>
>> Vivien
>
> There are mirroring ways yeah. That would be a better solution.
>
> Because there is biboumi but it basically just creates an IRC room in 
> XMPP.
>
>
> Also sneek should filter stuff probably. Because xmpp allows pictures 
> and long messages and such.
>
> So it shouldn't mirror everything as is. I don't know how possible it 
> is though. Maybe some custom setup of something.
>
>
> That said I do have my doubts whether this is more trouble than its 
> worth personally.
>
> Given that IRC and XMPP are two very different protocols that are 
> probably gonna attract a different community.

Agreed. Specifically, mobile XMPP clients work far, far better than 
their IRC counterparts out of the box. I think we'd see a lot of people 
come to the XMPP server due to it's great mobile accessibility.

In short, I think we should host our own XMPP server (maybe a VPS for 
uptime purposes? With media uploads and message logs, storage would be 
much more of a factor to consider compared to IRC) under the 
guix.gnu.org domain name and list it on the website. I think once we get 
to that stage, investigating how to keep track of message logs (perhaps 
mirroring logs to logs.guix.gnu.org, perhaps under a separate page to 
the IRC logs) will be vital in moderation efforts. Bridging would cause 
more problems and potentially solve a problem that we shouldn't want to 
solve (having one unified space).


>
>
> MSavoritias
>

Ada (adanska)



  reply	other threads:[~2023-12-11  6:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 17:22 RFI: Guix XMPP service MSavoritias
2023-12-08 18:43 ` Vivien Kraus
2023-12-08 18:56   ` MSavoritias
2023-12-10  3:53 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-10  7:27   ` MSavoritias
2023-12-10 14:43     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-10 15:45       ` MSavoritias
2023-12-10 15:56         ` Vivien Kraus
2023-12-10 16:04           ` MSavoritias
2023-12-11  6:53             ` Ada Stevenson [this message]
2023-12-13 19:49               ` RFI: Guix XMPP service. paid service? jbranso
2023-12-14  7:36                 ` Ricardo Wurmus
2023-12-14  8:28                   ` Ada Stevenson

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=db2ea64b-7b12-f3ef-c69c-4e637197da45@gmail.com \
    --to=adanskana@gmail.com \
    --cc=email@msavoritias.me \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).