From: David Wei <dw@davidwei.uk>
To: Mathieu Masson <mathieu.kernel@proton.me>, Jens Axboe <axboe@kernel.dk>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>, io-uring@vger.kernel.org
Subject: Re: [Announcement] io_uring Discord chat
Date: Fri, 17 May 2024 17:52:31 -0700 [thread overview]
Message-ID: <740aed6f-2ebc-4ad8-807b-bf1cef719313@davidwei.uk> (raw)
In-Reply-To: <ZkfZIgwD3OgPSJ8d@cave.home>
On 2024-05-17 15:24, Mathieu Masson 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/
This looks and feels more like a chat/forum hybrid with discussion
threads etc. I strictly prefer chat's lower friction but understand that
it makes it difficult to archive vs threads.
How are the threads created? Is it done at the start by the author? Or
can someone just type and start a convo in a generic stream e.g.
Filesystems, then an admin later groups the discussion?
next prev parent reply other threads:[~2024-05-18 0:52 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
2024-05-17 23:52 ` Jens Axboe
2024-05-17 23:51 ` Jens Axboe
2024-05-18 0:52 ` David Wei [this message]
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=740aed6f-2ebc-4ad8-807b-bf1cef719313@davidwei.uk \
--to=dw@davidwei.uk \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
--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).