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,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,URIBL_RED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 206C91F5AE for ; Mon, 26 Apr 2021 16:44:59 +0000 (UTC) Received: by mail-qt1-x831.google.com with SMTP id z25so19334576qtn.8 for ; Mon, 26 Apr 2021 09:44:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=8MQrxvVeLvImuLzO+VDg0koAzcnD/e6XT0p7JMc8M+U=; b=Mi6DHL27G1tla3DAMfymz9HsaS0cKgtuYB+J+/feqNmuH7Nk7tnE4ZH1OH6hKr+CgD miX8MuqsQ1h3rvwFzI5cTVvlEqCAvp5lyhxsJ51e4QC1b2zayl6/dryMSOCPfQLph7ho haL8L7CNzKMgv0ZrYVRmyr0qVJI+XFFRApRGg= 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:mail-followup-to :mime-version:content-disposition; bh=8MQrxvVeLvImuLzO+VDg0koAzcnD/e6XT0p7JMc8M+U=; b=TdxlqJ+EmxdFmXZ6Qg9YXW8iqlY5AYsaRlcAUoE7YuI5KS69B1L7HXm8X1KSpiZbqp k6CatcMFPn4LYiOgxHvpEdfwTXOhOzIXx7wDKkKctt6oyhYahQJ2vfcM9sshNSQdyJVP WZXHs/TlTpTIWXy7H0m9ecruJFBCCurzHY5RXUwP5zMOTEgqUeEvcxyBiFnLNabWtQ60 QwDCSkRmOkc33Mc04Pd729cUjt9w9VTv+RXN4jqd31FNg4nN5atp0EVzYnQcKV3Qwqnd zDQnjLm1Clj1Ki7A0Vl8VTKQ8Vpg9ppBKtHraGbuPXhJ52TCPFaBRgh49ZCz8VQQ3JTn MHAg== X-Gm-Message-State: AOAM530gT7y/x/x7sN5L/Z4ODx+jSC6a7fLRemcmiVfZVPLWgktgOXrt Gu2m3D+91FNUA5YhIISbv8l9OdMuOstwQX3L X-Google-Smtp-Source: ABdhPJw+4+RJzBH13cJVL+ps9kFQwsdmqLajel6/JENvENGOKZbkeByV+Pdj3ooWJopaC1cXJ5jm2Q== X-Received: by 2002:ac8:7dc2:: with SMTP id c2mr6091181qte.258.1619455497117; Mon, 26 Apr 2021 09:44:57 -0700 (PDT) Received: from nitro.local (bras-base-mtrlpq5031w-grc-32-216-209-220-18.dsl.bell.ca. [216.209.220.18]) by smtp.gmail.com with ESMTPSA id q84sm537378qke.13.2021.04.26.09.44.56 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Apr 2021 09:44:56 -0700 (PDT) Date: Mon, 26 Apr 2021 12:44:54 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: lei-managed pseudo mailing lists Message-ID: <20210426164454.5zd5kgugfhfwfkpo@nitro.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: One of the services I think would be interesting to provide is ability for people to subscribe to "curated saved searches". For example, a kernel subsystem maintainer can define a set of query parameters (a thread mentions these files/functions/terms, etc), and allow others to follow this saved search either by defining it as a remote source for their own lei command, or by subscribing to it as they would to any regular mailing list. The latter is specifically something I think would be of interest to kernel folks, so I envision that we'd have something like the following: - a maintainer publishes a configuration file we can pass to lei - our backend lei process uses all of lore.kernel.org sources to create and continuously update a new public-inbox repository with matching search results - we set up a mlmmj list that doesn't receive any direct mail but is only fed from saved search results; people can subscribe/unsubscribe as they would with any other mlmmj list Any particular reason this wouldn't work? -K