From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Mathieu Masson <mathieu.kernel@proton.me>
Cc: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [Announcement] io_uring Discord chat
Date: Fri, 17 May 2024 19:03:36 -0400 [thread overview]
Message-ID: <87ttiwt513.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <ZkfZIgwD3OgPSJ8d@cave.home> (Mathieu Masson's message of "Fri, 17 May 2024 22:24:37 +0000")
Mathieu Masson <mathieu.kernel@proton.me> writes:
> On 17 mai 13:09, Jens Axboe wrote:
> Not to start any form of chat platform war, but the rust-for-linux community has
> been using Zulip for a while now. At some point they made the full message
> history live accessible without an account :
>
> https://rust-for-linux.zulipchat.com/
>
>
> It is even search-able apparently, which is quite appreciable as an outsider
> who just wants to follow a bit in a more informal way than the ML.
I have no objection to Zulip if that is deemed better by the community.
I have never used Discord until today either, and I chose it because I
had heard the name before and Jens mentioned he uses it. It seems a quite
popular service nowadays, so I'd expect more people to already have an
account there than on Zulip.
But I agree that being searchable is essential. For that, I was looking
into this:
https://www.linen.dev/
which apparently turns discord channels into a read-only, Google-indexed
interface.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2024-05-17 23:03 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
2024-05-17 19:46 ` Jens Axboe
2024-05-17 22:24 ` Mathieu Masson
2024-05-17 23:03 ` Gabriel Krisman Bertazi [this message]
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 \
--in-reply-to=87ttiwt513.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=mathieu.kernel@proton.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.
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).