Barry Warsaw writes:
> > - archive links that won't break if the archive is rebuilt
>
> Yes, this is absolutely critical, in fact, I'd put it right at the
> top of the list, even more so than a u/i overhaul. Stable urls, with
> backward compatible redirecting links if at all possible, wo
> "st" == Stephen J Turnbull
> "Re: [Mailman-Developers] Improving the archives"
> Wed, 04 Jul 2007 16:49:58 +0900
st> The main drawback to using Message IDs that I can see is that
st> broken MUAs may supply no Message-ID, or the same one
st> repeatedly. In the former cas
I'm all for someone taking ownership of this long-neglected component --
thank you for doing so!
Barry Warsaw wrote:
> Maybe a way to think about this is that the canonical url is based on
> the message-id, but then there's some way to distill even this down
> to a tinyurl or simple integer t
>Maybe a way to think about this is that the canonical url is based on
>the message-id, but then there's some way to distill even this down
>to a tinyurl or simple integer that would be stable in the face of
>full archive regenerations.
I'd suggest the reverse. Keep the canoncical archive URL shor
>In which case [the message body link] would be set to something like.
>
>http://third-party-service/[EMAIL PROTECTED]
Just for fun, I did a trial implementation. It works, but the URLs are
too long.
For example, the URL below spends 59 characters on the messag-id, and
27 characters on the listnam
