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-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) (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 AE4A91F4C0 for ; Thu, 24 Oct 2019 21:21:11 +0000 (UTC) Received: by mail-qt1-x841.google.com with SMTP id z22so43967qtq.11 for ; Thu, 24 Oct 2019 14:21:11 -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:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=pqkwwQEEM2wLCXQEsU8IRWulb1Y7OgRWnB0NoCmSQDM=; b=gwGk+Y+/1x0QHHjj2jTb16jMKZ2EZWn3uwdX/vU2Qnd/ziyPxwonbQHIW6gwL793m1 wHo4+UiXUAi/GGIizAEpHpSNdNHqkFPPXNwC+IsxZ9saoICjdiIW0AhE7Q9UoVKSOxVl ONGQenyAyru6eQ+uoOAp1h4sIA2ZXK/fbZ+D8= 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 :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=pqkwwQEEM2wLCXQEsU8IRWulb1Y7OgRWnB0NoCmSQDM=; b=SGVPq67rnFbnGJ5p1V40EAkwbkvpp6WcepmGcfAIKQC+aJopZCNjGZP+5IhfKOmrQ4 fU3A3wTwQuPW289Z0fpp5UtAEMjXUYa/jtHusl+BTqhzmIWgYmq0rxEJA8OXhBP/09Az VF050MIbL0b+OGSHf2SjSaDKMlkrIy6IzQtWvZ2vf7YS6ljeSBuVhER5ce0samQ4BVZ8 rHqJqWvClW3560eH8GjhHkv3m0Z3tP6tZmRdYS76ixF0P8IAvpJYNWANQSWGeeNHJgY5 8IqFtk5zExMOBS5PmufDdbWuABM0yPY2qCGQ2z26n7/lXamkZynRRYtYlmtWe7NzNrCU 79xQ== X-Gm-Message-State: APjAAAXKr0AXDOjjIRnY3iCdgV/btoLUv+K7rB/Pqn80yBJWReFwprzD T69tlyEQZcHDGnY/yrjHxv1wBSpSsuw= X-Google-Smtp-Source: APXvYqwAzlFZ7e2IGI9wJ4QrYxD0yxPvMVlSA/l24StaMtiFgAyFFzdFhPDA0e801CFaTsmLjn8luQ== X-Received: by 2002:ad4:4bd1:: with SMTP id l17mr28306qvw.58.1571952070209; Thu, 24 Oct 2019 14:21:10 -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 h20sm6635qtp.93.2019.10.24.14.21.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Oct 2019 14:21:09 -0700 (PDT) Date: Thu, 24 Oct 2019 17:21:08 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: RFC: monthly epochs for v2 Message-ID: <20191024212108.zfbwh7bmfbo3cgu5@chatter.i7.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20191024195304.5b7zlx7e3vxfxmtg@chatter.i7.local> <20191024203503.GA31522@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20191024203503.GA31522@dcvr> User-Agent: NeoMutt/20180716 List-Id: On Thu, Oct 24, 2019 at 08:35:03PM +0000, Eric Wong wrote: >Epoch size should be configurable, yes. But I'm against time >periods such as months or years being a factor for rollover. >Many inboxes (including this one) can go idle for weeks/months; >and activity can be unpredictable if there's surges. Okay. It did just occur to me that the manifest file carries the "last-modified" stamp, so it's possible to figure out which repositories someone would need by parsing that data. >> - if someone is only interested in a few months worth of archives, they >> don't have to clone the entire collection >> - similarly, someone using public-inbox to feed messages to their inbox >> (e.g. using the l2md tool [1]) doesn't need to waste gigabytes storing >> archives they aren't interested in > >NNTP or d:YYYYMMDD..YYYYMMDD mboxrd downloads via HTTP search >are better suited for those cases. I know you really like nntp, but I'm worried that with Big Corp's love of deep packet inspection and filtering, NNTP ports aren't going to be usable by a large subset of developers. We already have enough problems with port 9418 not being reachable (and sometimes not even port 22). Since usenet's descent into mostly illegal content, many corporate environments probably have ports 119 and 563 blocked off entirely and changing that would be futile. >If people only want a backup via git (and not host HTTP/NNTP), >it's FAR easier for them to run ubiquitous commands such as >"git clone --mirror && git fetch" rather than >"install $TOOL which may be out-of-date-or-missing-on-your-distro" I think that anyone who is likely to use public-inbox repositories for more than just a copy of archives is likely to be using some kind of tool. I mean, SMTP can be used with "telnet" but nobody really does. :) If we provide a convenient library that supports things like intelligent selective cloning, indexing, fetching messages, etc, then that would avoid everyone doing it badly. In fact, libpublicinbox and bindings to most common languages is probably something that should happen early on. -K