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: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id B3C561F670; Tue, 12 Oct 2021 12:28:02 +0000 (UTC) Date: Tue, 12 Oct 2021 12:28:02 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: Is it safe to round-robin the nntp server? Message-ID: <20211012122802.M615085@dcvr> References: <20210901203022.lmyudbbouxzt5rfr@meerkat.local> <20210901205413.GA11375@dcvr> <20210901205634.guu4p7jyty3ec7qe@meerkat.local> <20210901210342.GB11375@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210901210342.GB11375@dcvr> List-Id: Eric Wong wrote: > Konstantin Ryabitsev wrote: > > On Wed, Sep 01, 2021 at 08:54:13PM +0000, Eric Wong wrote: > > > Likely, it depends on how picky NNTP clients are. The one thing > > > that could differ is the "created_at" field in msgmap.sqlite3. > > > > Is that value taken from git repos, or generated during indexing? All 3 nodes > > replicating from the same set of sources, but they do indeed run the index > > hooks at slightly different times. > > Whenever public-inbox-init runs for v2 (first public-inbox-index for v1). Fwiw, it should be possible to automate ->created_at synchronization using Last-Modified from /_/text/config/raw. "lei add-external --mirror" or public-inbox-clone +index will both set ->created_at automatically to match Last-Modified of the origin: https://public-inbox.org/meta/20211012114705.383-10-e@80x24.org/ ([PATCH 9/9] www: _/text/config/raw Last-Modified: is mm->created_at)