From: Mathieu Masson <mathieu.kernel@proton.me>
To: David Wei <dw@davidwei.uk>
Cc: Jens Axboe <axboe@kernel.dk>,
Gabriel Krisman Bertazi <krisman@suse.de>,
io-uring@vger.kernel.org
Subject: Re: [Announcement] io_uring Discord chat
Date: Sat, 18 May 2024 08:31:36 +0000 [thread overview]
Message-ID: <ZkhnYZ28Fl3SkB_N@cave.home> (raw)
In-Reply-To: <740aed6f-2ebc-4ad8-807b-bf1cef719313@davidwei.uk>
On 17 mai 17:52, David Wei wrote:
> 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?
>
Yes that is exactly like that. It's a forum hybrid, akin to what Teams is
nowadays, all conversation are tied under a topic. It's at the start of a
conversation that an author starts a thread yeah, by choosing a title for it and
the stream in which it'll take place. This seems to be the trend among chat
platforms nowadays, to have everything under threads. Not that I particulary
like it but it has its advantages. If you want a more broader view, you can
combine streams, and there is even a "recent conversation" view that combines
unseen conversations from all streams.
I guess discord originating more in the gaming world kept the pure chat
approach. If we want something more lower friction discord is the way to go.
(I'd say IRC but I see in another message Jens said it's a no go).
next prev parent reply other threads:[~2024-05-18 8:31 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
2024-05-18 8:31 ` Mathieu Masson [this message]
-- 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=ZkhnYZ28Fl3SkB_N@cave.home \
--to=mathieu.kernel@proton.me \
--cc=axboe@kernel.dk \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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).