From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5A74C1F4C0 for ; Fri, 18 Oct 2019 19:03:09 +0000 (UTC) Received: by mail-qk1-x72d.google.com with SMTP id p10so6269751qkg.8 for ; Fri, 18 Oct 2019 12:03:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=jAUYl2LFHuI0nZ5F8d3gjdxT8OkBtQKPFPcAUvkEp1w=; b=aL58uY6E+x50boA50isn6YiJqJFSVPLSDQW4vuuBgUmQMJ6/dBBTBURVhjQa5vmufn UaPTEODAbr0lp9B6C1jIKbza+ksTLrBYw/zX5+6aAUH2YijiX7+KYt+AP7O8knDwrIzO 57epPQ2286uCelD/cHOkTnMSmPg5eRAbug2vA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=jAUYl2LFHuI0nZ5F8d3gjdxT8OkBtQKPFPcAUvkEp1w=; b=KSBW8WAxVaMp4FNEOp+hCZL9AppqzqjBZaua3mxbYGa2XmAVi/Irldzw/Sck10PCGz AmpmxrkTYyRF6ppKkID5HJOURP4JrtnPF2nVgeJbTXvNA7kuo0UbM6gy2LrvQ1runXGe Ff5QbytqkSQs4Jzb8dUJncF/Ew3LRy/0uasqHz//w5iTmzumNRvZlJKlOK13K5OqY+RQ 9OnnS6p5ycQWchB3uL0OJtBFVydZro9AvWYu4UJfJlHP3Nib7DsPoAYrQM8+csPa8kc/ zoYOTdT+dZnzjO1kt2QTzT7icn94A7MfsELcKpDUkpYeb4lF78/KSeO/r7CX8edAvrzO kF3Q== X-Gm-Message-State: APjAAAXWWOSYExomlLkjMSHsybtGeblWafm8JjRFhlz9JA/F2HEYdifK TunD6IoIJSVdIA7oICRUT4BKYw== X-Google-Smtp-Source: APXvYqwtHuwnjv/9Bx9H7PyX/F535XklC1Fgc/a3pl90xQFTJNF2ZNNNMj6R1h07U47KG+zDGwCEug== X-Received: by 2002:a05:620a:1030:: with SMTP id a16mr10113451qkk.150.1571425387725; Fri, 18 Oct 2019 12:03:07 -0700 (PDT) Received: from chatter.i7.local (192-0-228-88.cpe.teksavvy.com. [192.0.228.88]) by smtp.gmail.com with ESMTPSA id 194sm3154696qkm.62.2019.10.18.12.03.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Oct 2019 12:03:07 -0700 (PDT) Date: Fri, 18 Oct 2019 15:03:05 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: workflows@vger.kernel.org, meta@public-inbox.org Subject: Re: workflow problems and possible public-inbox solutions Message-ID: <20191018190305.GF25456@chatter.i7.local> References: <20191018032516.GB29290@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20191018032516.GB29290@dcvr> User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: On Fri, Oct 18, 2019 at 03:25:16AM +0000, Eric Wong wrote: >It seems like there's a bunch of problems the workflows@vger >list is trying to solve. Some can be solved independently >of others. > >Here's a summary of them and where items in >https://public-inbox.org/TODO list can be possible solution >(I'm not claiming it can solve everything :P) Well, then you'd have to rename the project as "emacs". :) >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. >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. >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. -K