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.2 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-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 C44351F461 for ; Thu, 27 Jun 2019 18:42:54 +0000 (UTC) Received: by mail-qk1-x735.google.com with SMTP id i125so2639269qkd.6 for ; Thu, 27 Jun 2019 11:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=kUFmlI30+ST65/b4/OCPjUzxdDg4UBcuqN1NHsC/+gs=; b=GaODzU4p6lEWaiQQpwr5OESZeFbIuYFgLF8P1Ib+utb+R5bwV1l3IHIa8Fy367eS7c yZnmpyBu5yPsEeq5+APwQSedlQFrCvgEbkV+kFly3rtHZ6VRXZ5UFapi0WMFkKXsnh+m C41qG9S9ekZR4nwnLCRcWPuEG38+tPfn0M/io= 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:subject:message-id:mime-version :content-disposition:user-agent; bh=kUFmlI30+ST65/b4/OCPjUzxdDg4UBcuqN1NHsC/+gs=; b=QxBmENzSW/ZooeH0VIbEzQvz1LQ/Y4hVAUuY0FyCh207XmI9+fskEMic/QiSI8MPTQ w0Ob6JkCAzzplLSREehi3OwHgy06hBDzyzxwZ7CJyCzaWd2KDqcOzahlS1sl5ZlvgLc4 CzwIuE8Ye+N4FlfpLJrC6UtJEFxWzfT67PjMTrVKy1IEjE+EprmX7W0mLpQE14Z4D3HB eBwys1nJOE7ttbfXlzuuwkgGrkjMn8EkbdYrcxy+hz5PCFg+64doR5lHEAExCd45lbrt NmbnJnYaxgR0lOfeU/ZiHk9iamhnZbIaVzeSme2SkfXW7mG7Y7lKg8xCPUDPeGMNAiZg YhKA== X-Gm-Message-State: APjAAAXhWYbzubVE0jHsjW7Cb0DjyVEsFkfx/LCYbcKhUQhwDwGusRpa UT4oPPHzYhtoArKIyc2duFS7Wgzchzo= X-Google-Smtp-Source: APXvYqw0L4+zOUkYlvRrfGCg5QVpYBBl1/L7ipBo7AONYPmOPdMhBQJXhTBjhh9yljVxI5KdJ/JghA== X-Received: by 2002:a37:dcc7:: with SMTP id v190mr4885020qki.286.1561660973279; Thu, 27 Jun 2019 11:42:53 -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 a21sm1351494qkg.47.2019.06.27.11.42.52 for (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 27 Jun 2019 11:42:52 -0700 (PDT) Date: Thu, 27 Jun 2019 14:42:51 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: RFC: marking spam via refs/notes/spam to hide it Message-ID: <20190627184251.GC14570@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline User-Agent: Mutt/1.12.0 (2019-05-25) List-Id: Greetings: I'm reluctant to delete spam because it rebases the repository -- for large ones this can cause excessive downloads to mirrors. A thought occurred to me -- would it make sense to just hide spam from the frontend? E.g.: public-inbox-hide linux-kernel message@id This would do the following: - remove that message from search databases - attach a refs/notes/spam git-note to that commit - tell public-inbox-init/reindex to ignore this commit in the future Seems like it would be easy to do and would give a way to remove spam without needing to edit git history. -K