Lars Eggert wrote:
all this is about archive features, not about archive
longevity/availability. I agree that they are nice
features, maybe even essential ones, but availability
trumps them all.
I use GMaNe for 5+ years, sometimes there are glitches,
as with IETF lists hosted by the IETF, only different.
If you try to build new archives based on whatever you
find somewhere it would be a huge project.
This is the case even for recently concluded WGs such
as pki4ipsec or, ahem, infamous WGs such as newtrk.
<http://dir.gmane.org/gmane.ietf.newtrk> NNTP tells
me that GMaNe has 1214 articles (up to 2006-06). It's
hard to tell what Google knows about this, you could
try two patterns:
<http://permalink.gmane.org/gmane.ietf.newtrk/*>
<http://article.gmane.org/gmane.ietf.newtrk/*>
However cross-posted articles to more than one list
available on GMaNe will only get an URL in the first
group. If somebody posted to the general list *and*
Newtrk (that happened) it would AFAIK get only one
permalink on the general list.
To get around this you could try the URL patterns
<http://permalink.gmane.org/gmane.ietf.*>
<http://article.gmane.org/gmane.ietf.*>
But then you'd get articles more than once if they
are available under different patterns. Maybe you
could use specific patterns for lists only on GMaNe,
and general patterns with a "negative score" to get
your preferred archives for other lists first.
Google will anyway add its own scoring ideas, CSEs
are rather fuzzy whatever you do.
Frank
