ietf
[Top] [All Lists]

Re: new ietf mail archive? permanent urls?

2016-03-21 06:48:31
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_YI5r9wdoesn't work 
as I might expect.


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:
https://mailarchive.ietf.org/arch/msg/list/YYYY/MM
gives the entire month, etc.


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.


thanks
Lloyd Wood lloyd(_dot_)wood(_at_)yahoo(_dot_)co(_dot_)uk 
http://about.me/lloydwood 


----- Original Message -----
From: Henrik Levkowetz <henrik(_at_)levkowetz(_dot_)com>
To: lloyd(_dot_)wood(_at_)yahoo(_dot_)co(_dot_)uk; IETF Discussion 
<ietf(_at_)ietf(_dot_)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(_dot_)wood(_at_)yahoo(_dot_)co(_dot_)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

<Prev in Thread] Current Thread [Next in Thread>