Subject:
|
Re: Message-ID -> Article number
|
Newsgroups:
|
lugnet.admin.nntp
|
Date:
|
Mon, 18 Dec 2000 17:57:21 GMT
|
Viewed:
|
386 times
|
| |
|
|
Todd Lehman wrote:
>
> [redirecting to .admin.nntp]
>
> In lugnet.admin.general, Fredrik Glöckner writes:
> > In USENET, an article is refered to by it's Message-ID. Now, LUGNET
> > is not USENET, and here articles are normally refered to by the
> > article number on the server. This makes it a bit hard for me (or
> > anyone else who reads from the SMTP or NNTP interface) to refer to
> > articles.
> >
> > Say I am writing an article and want to refer to an older article by
> > myself or anybody else. I know the Message-ID of the article in
> > question, but I cannot find the article number on the LUGNET server
> > unless I fire up my dial up connection and start searching for it.
> > And with the search function out of order, this is quite hard.
> >
> > So what I would like is a way to refer to articles on LUGNET by their
> > Message-ID. For example something like this:
> >
> > http://news.lugnet.com/message.id/<Message-ID>
> >
> > So that I can simply plug in the Message-ID and post a link to it.
>
> I would really hate to see NNTP Message ID's floating around in HTTP URLs.
>
> A workaround is simply to use a standardized NNTP URL format -- for example:
>
> news://lugnet.com/qrd1yv57q2n.fsf@eos.uio.no
I'd hate to see these sorts of references. I'm not always browsing the
web interface in a browser that I want the news reader to come up in
(and such a reference will be useless to anyone who can't access the
nntp server).
> That's postable as-is.
>
> Or, if you want to convert that to an HTTP URL, it's as easy as looking at
> the Xref header on the message served directly from the NNTP server, which
> in the above case is:
>
> Xref: lugnet.com lugnet.admin.general:8505
>
> and simply transmogrify that into:
>
> http://news.lugnet.com/news/display.cgi?lugnet.admin.general,8505
>
> which automagically redirects to:
>
> http://news.lugnet.com/admin/general/?n=8505
I'd love to see a header which directly included this URL, it would make
life a little easier.
--
Frank Filz
-----------------------------
Work: mailto:ffilz@us.ibm.com (business only please)
Home: mailto:ffilz@mindspring.com
|
|
Message has 2 Replies:
 | | Re: Message-ID -> Article number
|
| (...) It would still not solve the problem of refering to an article which is refered to by an article you have. Say you have a bunch of LUGNET articles downloaded locally. You want to refer to the parent of an article you have, but you don't have (...) (24 years ago, 19-Dec-00, to lugnet.admin.nntp)
|
Message is in Reply To:
| | Re: Message-ID -> Article number
|
| [redirecting to .admin.nntp] (...) I would really hate to see NNTP Message ID's floating around in HTTP URLs. A workaround is simply to use a standardized NNTP URL format -- for example: news://lugnet.com/qr...eos.uio.no That's postable as-is. Or, (...) (24 years ago, 18-Dec-00, to lugnet.admin.general, lugnet.admin.nntp)
|
10 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
