From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: workflows@vger.kernel.org, meta@public-inbox.org
Subject: Re: workflow problems and possible public-inbox solutions
Date: Sat, 19 Oct 2019 00:29:28 +0000 [thread overview]
Message-ID: <20191019002928.GB20824@dcvr> (raw)
In-Reply-To: <20191018190305.GF25456@chatter.i7.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Fri, Oct 18, 2019 at 03:25:16AM +0000, Eric Wong wrote:
> > 1. vger deliverability problems to major mail providers
> >
> > (NNTP|public-inbox) => POP3 bridge, since all major providers
> > support importing mail from POP3.
> >
> > https://public-inbox.org/meta/20160411034104.GA7817@dcvr.yhbt.net/
> >
> > Locally-run NNTP -> mail fetchers can also work, but requires
> > more effort to setup.
>
> There is also this:
> https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/l2md.git/
>
> With a bit more tweaking (see TODO), it can be made into a very nice generic
> interface tool -- in fact, I hope to use it at some point for feeding
> patches into patchwork instead of piping directly from postfix.
Looks like that still needs local storage? I'm planning a tool
which would work remotely while allowing local caching/memoization.
> > 2. attestation of messages
> >
> > Self-publishing "Sent Mail" folders via NNTP or git,
> > (similar to Certificate Transparency):
> > https://lore.kernel.org/workflows/20191010192852.wl622ijvyy6i6tiu@chatter.i7.local/
> >
> > This would provide redundancy, too; and it's probably more
> > usable and learnable than GPG :P
>
> Well, it still uses GPG, but it hides away the horrible parts. The easiest
> way to accomplish auto-signing is to create a dedicated ECC subkey and store
> it (and just it) in a dedicated dir used by the self-publishing tool.
Self-hosting an .onion would get rid of the need for GPG.
That should be doable on most home Internet connections, but
requires constant uptime... But more self-hosting and not
having to pay registrars is good :>
HTTPS still relies on trust authorities, and it's "good enough"
for a lot of people so probably OK... *shrug*
> > 4. secret exchanges for embargoed issues
> >
> > No idea, really; not my department :P
> >
> > It would be good if all messages in the exchange can be
> > published and mirrored once the embargo is lifted, though.
>
> There is ongoing separate effort to address this, using remail:
> https://git.kernel.org/pub/scm/linux/kernel/git/tglx/remail.git/
>
> I haven't started implementing it yet, but my hope is to provide builtin
> archives that can be released once the embargo is lifted.
Cool :>
prev parent reply other threads:[~2019-10-19 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 3:25 workflow problems and possible public-inbox solutions Eric Wong
2019-10-18 19:01 ` Eric Wong
2019-10-18 19:03 ` Konstantin Ryabitsev
2019-10-19 0:29 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191019002928.GB20824@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).