I have good 'ole Voyager suite with Newsagent.
During the past 2 or 3 weeks, it seems that News Arts I have posted, haven't
appeared. Has anyone had the same problem ?
John N.
--
From Glorious Gloucestershire, near Lydney, using :------------
_ _________________________________________
/ \._._ |_ _ _ /' Orpheus Internet Services
\_/| |_)| |(/_|_|_> / 'Internet for Everyone'
_______ | ___________./ http://www.orpheusinternet.co.uk
> Hello All,
>
> I have good 'ole Voyager suite with Newsagent.
>
> During the past 2 or 3 weeks, it seems that News Arts I have posted,
> haven't appeared. Has anyone had the same problem ?
I have seen the odd post from you - maybe you've killfiled yourself :-)
Seriously, has Paul changed the name of your news server in the last
couple of weeks? I know he has redirected it in some way.
No doubt he'll be along with the definitive answer.
Cheers,
Ray D
And me2
Ben
--
_ __________________________________________
/ \._._ |_ _ _ /' Orpheus Internet Services
\_/| |_)| |(/_|_|_> / 'Internet for Everyone'
_______ | ___________./ http://www.orpheusinternet.co.uk
Revd Ben Crick BA CF <ben.crick[at]argonet.co.uk> ZFC Os
232 Canterbury Road, Birchington on sea, Kent CT7 9TD (UK)
Acorn RPC700 Kinetic RO 4.03 with Castle Iyonix RO 5.13 Ethernet
* God promises a safe landing, not a calm passage.
> In article <na.2de32e4f03.a...@orpheusmail.co.uk>,
> John Nolan <john....@orpheusmail.co.uk> wrote:
>> Hello All,
> Hi
>> I have good 'ole Voyager suite with Newsagent.
> me2
>> During the past 2 or 3 weeks, it seems that News Arts I have posted,
>> haven't appeared. Has anyone had the same problem ?
> I post quite a bit to several groups, and have had everything appear.
Your article arrived, but I certainly never got John Nolan's original.
(Using NetFetch.) That's not uncommon in my experience - answers to
articles appear where I have not seen the originals. Happens with
Archive-on-Line, too. An argument against excessive 'snipping',
perhaps, otherwise one has no idea what the discussion is all about.
Philip.
--
Philip Draper
Me too.
Mine have appeared, but I didn't see John's original message!
Alan Griffin
> (Using NetFetch.) That's not uncommon in my experience - answers to
> articles appear where I have not seen the originals.
I'd noticed this, too; and not 'just recently'.
--
BW Chris F. [ British Iyonix, RISC OS 5.13 & A9 ]
> In message <6fa835d2...@borehamh.demon.co.uk>
> Philip Draper <Phi...@borehamh.demon.co.uk> wrote:
>
> > (Using NetFetch.) That's not uncommon in my experience - answers to
> > articles appear where I have not seen the originals.
>
> I'd noticed this, too; and not 'just recently'.
That's how usenet works.
Originals have to migrate their way from the nntp server they were first
posted on across the world to all the 'peered' nntp servers, which isn't
instant.
Replies are posted to the nntp server that the replier uses, and then start
being replicated across all nntp servers.
You can easily see replies before earlier posts.
Also, when eg I connect to my nntp provider, my news client first uploads
posts I'm sending, then downloads new posts from the groups I read. That
always includes the posts I just uploaded; I'm probably the first person in
the world to get the public versions of those replies.
--
Jeremy C B Nicoll - my opinions are my own.
Email sent to my from-address will be deleted. Instead, please reply
to newsre...@wingsandbeaks.org.uk replacing "nnn" by "284".
> You can easily see replies before earlier posts.
>
> Also, when eg I connect to my nntp provider, my news client first uploads
> posts I'm sending, then downloads new posts from the groups I read. That
> always includes the posts I just uploaded; I'm probably the first person in
> the world to get the public versions of those replies.
>
OK. But I think that, sometimes, I never get the originals.
--
BW Chris F. [ British Iyonix, RISC OS 5.13 & A9 ]
RISC OS: driven by enthusiasts.
> In message <gemini.kw6uw...@wingsandbeaks.org.uk.invalid>
> Jeremy Nicoll - news posts <jn.nntp....@wingsandbeaks.org.uk> wrote:
>
> > You can easily see replies before earlier posts.
> >
> > Also, when eg I connect to my nntp provider, my news client first
> > uploads posts I'm sending, then downloads new posts from the groups I
> > read. That always includes the posts I just uploaded; I'm probably the
> > first person in the world to get the public versions of those replies.
> >
>
> OK. But I think that, sometimes, I never get the originals.
You use... giganews? Are they reliable?
It can't be that the originals haven't been posted, because if that were the
case no-one could have replied to them, and you (and others) have seen
replies.
So the problem is one of:
- your news provider has not received its copies of the earlier posts;
- if you suspect that, you'd need to talk to your provider
- your news fetcher has not fetched them;
- the fetcher's logs would be a good place to look for specific posts
not being processed (google will show you earlier posts in threads
even if no-one has referenced them in a reply)
(You might have a problem if you use more than one news provider and
if they number their posts differently. There's two ways to fetch
news posts - one "NEWNEWS" asks the server to provide any post that
it acquired after a certain date or time (but not many nntp servers
offer this and not many fetchers support it either). The other way
keeps track of the posts you've already seen (by their internal
server-assigned number) and asks for posts numbered higher than the
highest one you already fetched. If there are numbering errors or
you fetch from different servers which use different numbering
schemes and your fetcher doesn't keep the numbers separate for each
server, it'll certainly go wrong. NEWNEWS, if you have the choice,
is better because it's completely independent of what the server
administrators do with their numbering schemes.)
- your news fetcher has fetched them but it's then lost them
- I think that's unlikely...
- your news fetcher has fetched them and given them to your news client
and it has lost them. If you think this is happening you'd probably
need to make a date/time-stamped copy of each file of fetched posts
before they're handed to the client for debatching. It's the only
way you could be certain they'd arrived on your machine.
The 'loss' could happen for good design reasons, with Pluto, if one
turned on an option to only keep 1 instance of cross-posted posts. If
an article was cross-posted eg to comp.sys.acorn.apps and also to
comp.sys.acorn.programmer, Pluto would put the single copy it was
keeping into the csa.apps box; if you deleted it from there because
you thought the thread was of no interest, or because you'd read it
and didn't need to keep it, then you'd find it 'missing' from the
thread in csa.programmer.
Maybe your client is doing something similar.
> In message <gemini.kw6uw...@wingsandbeaks.org.uk.invalid>
> Jeremy Nicoll - news posts <jn.nntp....@wingsandbeaks.org.uk> wrote:
>> You can easily see replies before earlier posts.
>>
>> Also, when eg I connect to my nntp provider, my news client first uploads
>> posts I'm sending, then downloads new posts from the groups I read. That
>> always includes the posts I just uploaded; I'm probably the first person in
>> the world to get the public versions of those replies.
>>
> OK. But I think that, sometimes, I never get the originals.
It certainly happens here, but only in one (non-RISC OS) newsgroup.
Jeremy has pointed a suspicious finger at Giganews, and Orpheus uses
the Giganews server, I think.
With best wishes,
Peter.
--
Peter, \ / zfc Yb \ Prestbury, Cheltenham, Glos. GL52
Anne \/ __ __ \ England.
and / / \ | | |\ | / _ \ http://pnyoung.orpheusweb.co.uk
family / \__/ \_/ | \| \__/ \______________ pny...@ormail.co.uk
> > OK. But I think that, sometimes, I never get the originals.
>
> It certainly happens here, but only in one (non-RISC OS) newsgroup.
> Jeremy has pointed a suspicious finger at Giganews, and Orpheus uses
> the Giganews server, I think.
Jeremy's response is a lot for me to take-in. The operative words, in
my case, are 'I think that'. It might be a perception issue. I'll try
to monitor for a while. It's not a major problem for me because I
usually manage to work-out the main thrust.
I did look inside !Newshound 1.50-32 but I don't see any reference to a
named server.
I did find a reference in 'Choices/Misc' to running !FetchEnd (which
isn't set) but couldn't find any info on what it is for.
--
BW Chris F. [ British Iyonix, RISC OS 5.13 & A9 ]
Breakfast @ Foxfield Railway? Why not! (01782 259667)
> Jeremy's response is a lot for me to take-in. The operative words, in my
> case, are 'I think that'. It might be a perception issue. I'll try to
> monitor for a while. It's not a major problem for me because I usually
> manage to work-out the main thrust.
>
> I did look inside !Newshound 1.50-32 but I don't see any reference to a
> named server.
The server is specified in a file called xxxGroup inside !NewsHound.Choices,
where "xxx" is a three-letter mnemonic that NewsHound uses to identify the
server. NewsHound can operate with multiple servers at the same time.
Checking in NewsHound's choices will tell you which servers are active (if
you use NetFetch, it will usually be "dun").
> I did find a reference in 'Choices/Misc' to running !FetchEnd (which isn't
> set) but couldn't find any info on what it is for.
You can run a utility after news has been fetched, IIRC. Unless you know
what you're doing (and have a use for some post-processing of the downloaded
news), you are unlikely to want this on.
--
Steve Fryatt - Leeds, England
> That's how usenet works.
>
> Originals have to migrate their way from the nntp server they were first
> posted on across the world to all the 'peered' nntp servers, which isn't
> instant.
>
> Replies are posted to the nntp server that the replier uses, and then
> start being replicated across all nntp servers.
>
> You can easily see replies before earlier posts.
Indeed. This is particularly pronounced here, as I run my own local NNTP
server (Leafnode, on Linux, which effectively replaces NewsHound for my
setup). As such, my own posts only need go as far as the machine running
Leafnode before showing up in M-Pro again, whereas posts from others may tak
several hours to work through the system to reach my ISP's server and then
finally reach my own system.
It's worth remembering that because of this, duplicate replies often get
written by more than one person. You can't assume that someone who has just
said exactly the same thing as you in response to a post ever saw /your/
reply before they hit send on theirs. Allowing for the fact that many
people only fetch news every hour or so, or once a day, this delay can be
quite long.