warren (09/22/82)
It seems that every time someone raises a new issue with news, new articles on the same topic keep coming days later that appear as if the author is unaware of all of the previous discussion. Why not have postnews or inews or whatever check and see if the news submitter has read all of the articles in the categories to which she/he is posting. If not, the user should be warned and given the opportunity to read the new items before posting. This may cut down the amount of duplication in the stuff flying over the net. x
wagner (09/23/82)
Over in this corner of the net, we get articles all out of order. I routinely see replies several days before the question arrives. No doubt we, in ourr isolation, also duplicate suggestions/statements made elsewhere, since they seem to exhibit unpredictible transit times to us. Michael Wagner, UTCS
ech (09/23/82)
#R:ihnss:-16900:whuxlb:7700004:000:590 whuxlb!ech Sep 23 15:36:00 1982 Aha, excellent point, Warren! Now all we have to do is make sure that all the responses to an article arrive with the article... Seriously, how do you get around the variable latency in news item delivery? Respondents A and B may be an equal "net distance" from the original article (thus see it the same day), but may be arbitrarily far from one another. The best one can do is to see if you've seen all the locally received responses, but failing a notes-like interface and a willingness to use it broadly, there's no mechanical way to even match up items and responses. =Ned Horvath=
lepreau (09/27/82)
When contemplating a followup or reply, a useful command is "e-", which forgets that you saw the last article. Then when you've finished reading news, you can just readnews again and see any articles you considered replying to. The -/multiple newsgrps bug does not bite any of the <cmd>- constructs that I know of. -Jay Lepreau