From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: workflows@vger.kernel.org
Subject: Re: RFC: individual public-inbox/git activity feeds
Date: Fri, 18 Oct 2019 02:48:28 +0000 [thread overview]
Message-ID: <20191018024828.bifvcec36fvijyqb@dcvr> (raw)
In-Reply-To: <20191010235725.GA15427@dcvr>
Eric Wong <e@80x24.org> wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>
> <snip a bunch of stuff I agree with>
>
> > # Individual developer feeds
>
> <snip>
>
> > (With time, we can teach kernel.org to act as an MTA bridge that sends
> > actual mail to the mailing lists after we receive individual feed updates.)
>
> I'm skeptical and pessimistic about that bit happening (as I
> usually am :>). But the great thing is all that stuff can
> happen without disrupting/changing existing workflows and is
> totally optional.
Well, maybe less skeptical and pessimistic today...
Readers can look for messages intended for them on a DHT or some
other peer-to-peer system. Or maybe various search engines can
spring into existence or existing ones can be optimized for this.
Readers can opt into this by using invalid/mangled addresses
(e.g "user@i-pull-my-email.invalid"); and rely on that to find
messages intended for them.
Senders sending to them will get a bounce, see the address; and
hopefully assume the reader will see it eventually if any
publically-archived address is also in the recipients list.
Or an an alternate header (e.g. "Intended-To", "Intended-Cc")
can also be used to avoid bounces (but MUAs would lose those on
"Reply-All"), so maybe putting those pseudo-headers in the
message body can work.
This will NOT solve the spam/flooding/malicious content problem.
However, the receiving end can still use SpamAssassin, rspamd,
or whatever pipe-friendly mail filters they want because it
still looks like mail.
next prev parent reply other threads:[~2019-10-18 5:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 19:28 RFC: individual public-inbox/git activity feeds Konstantin Ryabitsev
2019-10-10 23:57 ` Eric Wong
2019-10-18 2:48 ` Eric Wong [this message]
2019-10-11 17:15 ` Dmitry Vyukov
2019-10-11 19:07 ` Geert Uytterhoeven
2019-10-11 19:12 ` Laurent Pinchart
2019-10-14 6:43 ` Dmitry Vyukov
2019-10-11 19:39 ` Konstantin Ryabitsev
2019-10-12 11:48 ` Mauro Carvalho Chehab
2019-10-11 22:57 ` Daniel Borkmann
2019-10-12 7:50 ` Greg KH
2019-10-12 11:20 ` Mauro Carvalho Chehab
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=20191018024828.bifvcec36fvijyqb@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--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).