all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bo0od <bo0od@riseup.net>
Cc: 48793@debbugs.gnu.org
Subject: bug#48793: Make guix room available over matrix
Date: Thu, 03 Jun 2021 00:20:05 +0200	[thread overview]
Message-ID: <87o8cnnc2y.fsf@nckx> (raw)
In-Reply-To: <a84bed4c-a926-94cd-6790-7bbde70a28c4@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

bo0od 写道:
> Im not sure im following, Does guix has its own room over matrix 
> or
> not? if yes what is it

There's #guix:libera.chat that Julien already pointed out.  It's a 
bridge to the official #guix channel at Libera.  Messages are sent 
back & forth between Libera and matrix.org.  I don't know if 
matrix.org supports Tor.

There's *also* #guix:matrix.org.  It is a ‘real’ Matrix 
channel/room, but it is not managed by the project and fewer core 
contributors lurk there.

> if not thats why i opened this ticket.

It's not really a bug, though, is it?  There's no official Guix 
Mastodon either.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-06-02 22:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 18:42 bug#48793: Make guix room available over matrix bo0od
2021-06-02 20:22 ` Julien Lepiller
2021-06-02 21:46   ` bo0od
2021-06-02 21:50     ` Julien Lepiller
2021-06-02 21:57       ` bo0od
2021-06-03 15:34         ` Bone Baboon via Bug reports for GNU Guix
2021-06-03 19:52           ` bo0od
2021-06-02 20:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-06-02 21:39   ` bo0od
2021-06-02 22:20     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-06-03 19:39       ` bo0od
2021-06-03 21:18         ` Julien Lepiller
2021-06-07 22:35           ` bo0od

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

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

  git send-email \
    --in-reply-to=87o8cnnc2y.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=48793@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.