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-vs1-xe43.google.com (mail-vs1-xe43.google.com [IPv6:2607:f8b0:4864:20::e43]) (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 F04621F462 for ; Mon, 10 Jun 2019 15:06:50 +0000 (UTC) Received: by mail-vs1-xe43.google.com with SMTP id g24so5530164vso.8 for ; Mon, 10 Jun 2019 08:06:50 -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=pS4qU2uJWiQi97tElpKP8tVhVZAfNpTghAhX5ygZN4c=; b=fI2xktJfurSX8x6+HiEdNREk2ls8dE6vzzXKxjkgecDjxIPv85+HN+rPMyoTTln73q fIgErPWMyWiCYGZGK5fwKgnGhru4flEbjd1gkeRtD0s/Xxz/D/R7hGyygfWU3AlNI5/H hCdPhABLWQAtFKjtH4eCELbSsgHis1Pcc2hg4= 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=pS4qU2uJWiQi97tElpKP8tVhVZAfNpTghAhX5ygZN4c=; b=TVB6z7A3goc/SoWCDhqphsmTKgoYRyUbgmdNqkRarVNJm+5U/umjYMEoR9nFwLFgJz o0l2maJDpoIwsxp5/pr2DM/a0MjOCWvUikV9QLJpenOZlNoWjAJDz2XePQnLcNltkCH0 +I4eJVUaHKpwblWtPVpYoIbL9Efq4PWA2UVvJ3EmwyObMWgRNffbQ0AUQe4w+ylyI3nl nVRyQ3HJ1E1OKry62/pX41A8T782NZnAa/jPorr1ROkuOy8B07iccrhCerfZaUpeH7WQ C5/9xzg3MINACc4X54yoKj2TbKDG3VSyPKBebCs2mVNlBQp88R1GMBCfGav/k8wLKIOp +0Bw== X-Gm-Message-State: APjAAAU3o0JISqECAxaVxdpID1xP/2nmhtDnowOv3ZRqvtR30UWv0SEM I8nojgREcaUu5QAxXDxzNGeCyg== X-Google-Smtp-Source: APXvYqw4Vsj8JucnREGr9OYe9u7T98f8VW/rZ88YCgiJIhzK9r528rXMCqJZyYZ0PJCJvEN/CSiCtg== X-Received: by 2002:a67:ead3:: with SMTP id s19mr4213743vso.147.1560179209543; Mon, 10 Jun 2019 08:06:49 -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 e7sm2544157vsc.28.2019.06.10.08.06.48 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 10 Jun 2019 08:06:48 -0700 (PDT) Date: Mon, 10 Jun 2019 11:06:47 -0400 From: Konstantin Ryabitsev To: "Eric Wong (Contractor, The Linux Foundation)" Cc: meta@public-inbox.org Subject: Re: [PATCH 00/11] v2: implement message editing Message-ID: <20190610150647.GA16418@chatter.i7.local> References: <20190609025147.24966-1-e@80x24.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20190609025147.24966-1-e@80x24.org> User-Agent: Mutt/1.11.4 (2019-03-13) List-Id: On Sun, Jun 09, 2019 at 02:51:36AM +0000, Eric Wong (Contractor, The Linux Foundation) wrote: >Some organizations are legally responsible for removing certain >content but prefer to edit out sensitive parts of a message >instead of purging it completely from history. > >We can build off existing purge functionality. Instead of >replacing a message with an empty file; we instead replace >it with the desired content. > >This ->replace method reindexes the modified message and >updates the corresponding git commit in case the subject >or authorship ident changes. > >A new tool, public-inbox-edit(1) wraps the new ->replace >functionality by providing an editable mboxrd (suitable >for publicinbox.mailEditor "mutt -f"). Thanks, Eric. I'm testing this out now. Quick question -- I'm assuming this can't be done online, while new messages are arriving, correct? Should the procedure be to stop incoming mail, perform the edits, then start the mail again? Best, -K