From: "Drew DeVault" <sir@cmpwn.com>
To: <bjorn@helgaas.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
<workflows@vger.kernel.org>
Subject: Re: matrix.org as a replacement for IRC?
Date: Tue, 14 Jan 2020 14:14:16 -0500 [thread overview]
Message-ID: <BZVR5M9SVTXV.1642VEAVLDJ2B@homura> (raw)
In-Reply-To: <CABhMZUUaEj7fme6OVa4sQmrUSYpumG-t-1KeACdFq-UDks5wdA@mail.gmail.com>
On Tue Jan 14, 2020 at 1:13 PM, Bjorn Helgaas wrote:
> I'd never heard of matrix.org and don't have an opinion either way. I
> do find IRC useful. Proxies make it much more useful, and if I have a
> choice, I'd rather not pay $50/year to irccloud just for a permanent
> presence.
>
> I'd be interested to hear the details of your NACK, because they'd
> likely be informative and useful to me.
$50/year is offset by one fewer cup of coffee per month.
In any case, bouncers are not as necessary as they might seem. The idea
of an infinite backlog encourages you to keep up with discussions you
missed, which is a bad way of approaching IRC. Docs don't live in IRC,
projects don't live in IRC, tickets don't live in IRC - any discussion
that people shouldn't be fine with missing should be summarized and
forwarded to a more appropriate medium.
I use a bouncer mainly because IRC is such an important part of my life
that it's helpful for organization, and it's nice for people to be able
to drop me a quick note while I'm offline. Nice, but easily replaced
with email for anyone without a bouncer.
next prev parent reply other threads:[~2020-01-14 19:16 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 [this message]
2020-01-15 12:46 ` Matthias Brugger
2020-01-14 13:59 ` Greg KH
2020-01-15 0:22 ` TAN: SSIA emails [was: matrix.org as a replacement for IRC?] Eric Wong
2020-01-15 4:44 ` matrix.org as a replacement for IRC? 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=BZVR5M9SVTXV.1642VEAVLDJ2B@homura \
--to=sir@cmpwn.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bjorn@helgaas.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 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 NNTP newsgroup(s).