All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@yhbt.net>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: workflows@vger.kernel.org
Subject: TAN: SSIA emails [was: matrix.org as a replacement for IRC?]
Date: Wed, 15 Jan 2020 00:22:48 +0000	[thread overview]
Message-ID: <20200115002248.GA27608@dcvr> (raw)
In-Reply-To: <87d0bmkx1w.fsf@linux.ibm.com>

"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> wrote:
> Was there any discussion around using matrix.org or any other
> alternative as a replacement for IRC? This should help to avoid setting
> up irc proxy to keep track of discussion when the users are not online.

Going off on a tangent here, I've been thinking about detecting
and displaying Subject-Says-It-All (SSIA) emails in a more
concise way for public-inbox.

That would give some benefits of chat and save readers' time in
having less text to wade through; while still retaining
threading and offline capability of email.

I'm not aware of any existing MUAs which support, it, though;
so I'm hesitant to have public-inbox be the first...

> IIUC both KDE and mozilla switched to matrix as their IRC replacement.

Not sure how those orgs operate, but I find synchronous
communication tiring and difficult when people are operating
between several different timezones.  It's especially difficult
when several topics are being discussed in parallel.

I still use IRC privately, but only with small groups and mostly
for non-technical topics ("watercooler talk"); but some of my
fellow chatters have been wanting to move over to proprietary
replacements :<

  parent reply	other threads:[~2020-01-15  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 13:05 matrix.org as a replacement for IRC? Aneesh Kumar K.V
2020-01-14 13:35 ` Drew DeVault
2020-01-14 19:13   ` Bjorn Helgaas
2020-01-14 19:14     ` Drew DeVault
2020-01-15 12:46       ` Matthias Brugger
2020-01-14 13:59 ` Greg KH
2020-01-15  0:22 ` Eric Wong [this message]
2020-01-15  4:44 ` Brendan Higgins

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=20200115002248.GA27608@dcvr \
    --to=e@yhbt.net \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=workflows@vger.kernel.org \
    /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 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.