public inbox for [email protected]
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected]
Subject: Re: [Announcement] io_uring Discord chat
Date: Fri, 17 May 2024 15:44:08 -0400	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]> (Jens Axboe's message of "Fri, 17 May 2024 13:09:16 -0600")

Jens Axboe <[email protected]> writes:

> Is it public - and if not, can it be? Ideally I'd love to have something
> that's just open public (and realtime) discussion, ideally searchable
> from your favorite search engine. As the latter seems
> difficult/impossible, we should at least have it be directly joinable
> without an invite link. Or maybe this is not how discord works at all,
> and you need the invite link? If so, as long as anyone can join, then
> that's totally fine too I guess.

It is as public as it can be right now with existing discord rules.  It
can not be made discoverable without a link yet, since it needs to be at
least 8 weeks old for that, from what I see.  I'm looking into that.

The invitation link doesn't expire and doesn't require any approvals. We can
safely place it in liburing documentation.  I mentioned it is revokable,
but that is a safeguard against spammers and needs to be done explicitly.

Let me know if you join. I'll add you as an admin.

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2024-05-17 19:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 18:51 [Announcement] io_uring Discord chat Gabriel Krisman Bertazi
2024-05-17 19:09 ` Jens Axboe
2024-05-17 19:44   ` Gabriel Krisman Bertazi [this message]
2024-05-17 19:46     ` Jens Axboe
2024-05-17 22:24   ` Mathieu Masson
2024-05-17 23:03     ` Gabriel Krisman Bertazi
2024-05-17 23:52       ` Jens Axboe
2024-05-17 23:51     ` Jens Axboe
2024-05-18  0:52     ` David Wei
2024-05-18  8:31       ` Mathieu Masson
  -- strict thread matches above, loose matches on Subject: below --
2024-05-18  0:25 Jason Bowen
2024-05-18  0:43 ` Jens Axboe

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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