Re: new ietf mail archive? permanent urls?

Henrik Levkowetz <henrik@levkowetz.com> Mon, 21 March 2016 12:47 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A630212D782 for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 05:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.9
X-Spam-Level:
X-Spam-Status: No, score=-106.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYT0mJw1qcuA for <ietf@ietfa.amsl.com>; Mon, 21 Mar 2016 05:47:25 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8276612D7A7 for <ietf@ietf.org>; Mon, 21 Mar 2016 05:47:25 -0700 (PDT)
Received: from [2a01:3f0:1:0:99f2:14ba:aea:9944] (port=63376 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <henrik@levkowetz.com>) id 1ahzEy-0001AY-Oh; Mon, 21 Mar 2016 05:47:25 -0700
To: lloyd.wood@yahoo.co.uk, IETF Discussion <ietf@ietf.org>
References: <56EFC6EA.7010406@levkowetz.com> <1228435241.2108560.1458560886818.JavaMail.yahoo@mail.yahoo.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <56EFED5A.7040807@levkowetz.com>
Date: Mon, 21 Mar 2016 13:47:22 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <1228435241.2108560.1458560886818.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:99f2:14ba:aea:9944
X-SA-Exim-Rcpt-To: ietf@ietf.org, lloyd.wood@yahoo.co.uk
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: new ietf mail archive? permanent urls?
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2JvZJQXLlOdATmgSVfQiQPC0MFU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2016 12:47:31 -0000

On 2016-03-21 12:48, lloyd.wood@yahoo.co.uk wrote:
> Hi Henrik,
> 
> 
> I'd be good with list/YYYY/MM/DD/identifier-hash (per Wordpress
> and in line with ISO8601 - none of that US MM/DD/YY funny stuff)
> added into the urls, allowing mails to be retrieved either with
> or without the date. (I presume the list id is optional as well
> but
> https://mailarchive.ietf.org/arch/msg/GKYUQNOssvg-JIsPfj90_YI5r9w
> doesn't work as I might expect.

No, the list is necessary.  That decision was based on the same message
sometimes going to multiple lists, and being archived as different
items for the different lists.  Yes, it would probably be possible to
pull out the right message without the list, but that becomes a GUI
headache when you find multiple matching items on different lists.

> if
> https://mailarchive.ietf.org/arch/msg/list/YYYY/MM/DD/
> 
> can return all emails to that list on that date, so much the better:

That sounds nifty, yes.

> https://mailarchive.ietf.org/arch/msg/list/YYYY/MM
> gives the entire month, etc.

Ack.

> https://mailarchive.ietf.org/arch/msg/GKYUQNOssvg-JIsPfj90_YI5r9w
> https://mailarchive.ietf.org/arch/msg/ietf/GKYUQNOssvg-JIsPfj90_YI5r9w
> https://mailarchive.ietf.org/arch/msg/ietf/2016/03/20/GKYUQNOssvg-JIsPfj90_YI5r9w
> 
> should return the same thing.

Well, not the first one, as indicated above.  That would mean guessing
which one to present, for messages going to multiple lists, and explicit
is better than implicit.  But I like the date-in-url enhancements.


Regards,

	Henrik


> 
> thanks
> Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 
> 
> 
> ----- Original Message -----
> From: Henrik Levkowetz <henrik@levkowetz.com>
> To: lloyd.wood@yahoo.co.uk; IETF Discussion <ietf@ietf.org>
> Sent: Monday, 21 March 2016, 21:03
> Subject: Re: new ietf mail archive? permanent urls?
> 
> Hi Lloyd,
> 
> On 2016-03-20 12:42, lloyd.wood@yahoo.co.uk wrote:
>> okay, I've finally belatedly noticed the new ietf mail archive.
>> (because I have a life these days.)
>>
>> Is e.g.
>> https://mailarchive.ietf.org/arch/msg/ietf/GKYUQNOssvg-JIsPfj90_YI5r9w
>> a permanent url? If not, should it be?
> 
> Yes, it is.  If you go and look at the message headers, you'll notice
> that there's even an Archived-At: header field which has that permanent
> url as its value.
> 
> 
>> (It's occasionally
>> useful to refer to emails directly, and cite text with urls, but
>> that doesn't look like a good choice. I mean, no date in url?
>> as a hint?)
> 
> Good point. I think it would be rather easy to add a date hint to the
> permanent URL, even if I think we'd still be using just the list and
> hash to identify and pull out the message at the server end.  The list
> is already in the URL (in the case of the URL above, the list identifier
> is the '/ietf/' part).
> 
> 
> Regards,
> 
>     Henrik
>