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.8 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_FILL_THIS_FORM_SHORT shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 4EB751F8C7 for ; Tue, 29 Jun 2021 20:10:50 +0000 (UTC) Received: by mail-qt1-x832.google.com with SMTP id w13so1312552qtc.0 for ; Tue, 29 Jun 2021 13:10: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; bh=kMhFC8fxDbPrL9jtJGWEH3f6cThntQGRKJKilce1KWw=; b=O0VlK3eIpNcv0NavH26QCPcDJZy4ayQr63WHiPBIDCY19tqv43bQmfyTsZRTD3Yvp2 yXlXfq5zd59TPWUSHCgV0uFtjB1+Kaig0n2XCCZLefuN5HhLz0Cho8lg6QZ/dqV79nXs bCrOTD7XjS3MvtQwQ/r+ZCeTTrAPndp/4yhlQ= 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; bh=kMhFC8fxDbPrL9jtJGWEH3f6cThntQGRKJKilce1KWw=; b=M8nzZTWIjvMc1sjhMoQ7nITuRymmREylra8hDmuLQwlBnbZoItuA47oZpgL49tqi7+ dVl8IG70YsAPA3fiwxHRYi12Z8l5eKfXTAMl0eZKubg7T8WSi4TOWxnnWI6s/tOCeMav HZl235qPOiz3GfBKmGylVYkr2dWnkOQipgAoIEAZLXeENS5gbROLaqaX73BcSq0RrhIW h4jBcvhATXMTG7BcwfdZi7CGWb9IGBhOvHaQZpsVL0hscTHLcN7Uo8zlKReZ8bjvOFMb 8hMUYl7AtCaf3yXNKnI+wF3LgznX1oDaP0f8alSXtDuwyxlZTwh1ys1hvqGBk/BkiaKe AXsw== X-Gm-Message-State: AOAM5339qTIJv3Fx1YIGqiJ2PvamFbdDtI1KPaWIyNODbjVc1I91PxzG x1srxSb7ftebOz69cDDiG5+X/A== X-Google-Smtp-Source: ABdhPJxom2DUaq27ClmDISWdcujGhr4ZlFX0v3h+eoqqLwGIZXpHPHCgWqT8EbD5xxXjyFxkrXZXdA== X-Received: by 2002:a05:622a:1aa4:: with SMTP id s36mr27887904qtc.337.1624997449122; Tue, 29 Jun 2021 13:10:49 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id c11sm9568749qth.29.2021.06.29.13.10.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Jun 2021 13:10:48 -0700 (PDT) Date: Tue, 29 Jun 2021 16:10:47 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Recording archiver origins in git Message-ID: <20210629201047.wfsjzlqiqyfuaopg@nitro.local> References: <20210628212610.zbexle2b2uvux2sd@nitro.local> <20210628221236.GA25399@dcvr> <20210629125626.c5e6ianh6yilbakp@nitro.local> <20210629195957.GA12571@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210629195957.GA12571@dcvr> List-Id: On Tue, Jun 29, 2021 at 07:59:57PM +0000, Eric Wong wrote: > > My thinking is that with mirrors of mirrors of mirrors, if someone submits a > > GDPR removal request, then there should be an easy way of figuring out where > > these requests should actually go. Maybe infourl can cover this, but it's less > > likely to be set up than an email address like postmaster@. So, I'm in favour > > of keeping that in the info record. > > I'm a little worried about it having too many directions > (e.g. webmaster vs postmaster) and something freeform like > infourl can cover it. Or we maybe something with user-defined > labels would work: > > contact = postmaster mail-admin@example.com > contact = GPDR https://our-lawyers.example.com/form.cgi > contact = webmaster web-admin@example.com Maybe more RFC2822-like: contact = postmaster contact = GPDR contact = webmaster Should be kosher with git-config and a bit more obvious that one is a label. > > I'm actually thinking the other way around -- only the 0.git (or whatever is > > the lowest number), simply because it's more likely to have that record. That > > is, unless you want to add functionality to automatically copy these from > > previous epochs on auto-rotation events. > > It should be easy to change this info down-the-line in case of > project name/hosting changes, forks, etc. So whatever's latest > should supercede the older. It would also allow partial mirrors > to work with only the latest epoch(s) (I expect a partial > mirrors of recent epochs to be more useful than mirrors with > only old epochs). OK, I'm not picky and it's easy to reverse the dir listing. I'll trial it out on some lore archives and then share the resulting hooks. -K