Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > aioe.system > #113

Re: Newsfeeds broken

Show all headers | View raw

Paolo Amoroso <estasi@aioe.org> wrote:
>Il 04/04/2016 03:17, David LaRue ha scritto:

>>Tried replying to one of my own messages in asl and this time it gave me
>>this id: here are a few:

>><nddq51$1st$1@theodyn.ncf.ca>
>><ndf4h5$6ch$1@theodyn.ncf.ca>
>><ndksnj$d60$1@theodyn.ncf.ca>

>my server never saw these articles.

>At the same time, you say

>>My Canadian friends, one of whom connects via FreeNet, and has posted
>>several times over the weekend in alt.support.lonliness doesn't propogate
>>to aioe.org.  Thus far we're not sure which ISPs the other two Canadians
>>are using that are posting but not being propogated.

>alt.support.LONLINESS is not carried by aioe.org and all articles sent 
>to that group are silently trashed. Even if i created it on my host, if 
>my other peers don't carry that group on their sites i don't receive 
>articles because they're dropped by those server before me in the 
>distribution chain. This makes useless to create it on my host before 
>establishing a feed with some server that carries it.

Of course you didn't create alt.support.lonliness. There is an
alt.support.loneliness, which you created locally.

>could you provide me a list of groups where articles are missing?

Please don't create groups like alt.support.lonliness. I can't find it
created anywhere, but if it exists, it's because some server is set up
to create any newsgroup based on obvious syntax errors in the group name
committed by the author of the article just to show off about having
a more complete set of newsgroups than some other server. Such articles
should be rejected till the author corrects the syntax error.

Misspelling a group name on the Newsgroups header is one of the more serious
errors that should lead to an article being rejected, not propagated.

>btw nowadays it's impossible to guarantee a good propagation for 
>'unofficial' alt.* groups since nobody maintains usenet servers no more 
>and so it's hard to communicate with the other newsmasters about lacks 
>of propagation in some groups.

Actually, it's the same now as it was in the beginning, that servers would
create an alt.* newsgroup because a user requested its creation. alt groups
are no more unofficial today than in the past. The hierarchy isn't
administered and its up to the proponent to work at propagation.

Administered hierarchies don't always fare any better as there are
servers that don't accept checkgroups from the hierarchy administrators
and create groups in administered hierarchies upon user request. It
means the proponent must work and it's the same amount of work to get a
group going whether it's named into alt.* or an administered hierarchy.

Back to aioe.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Newsfeeds broken David LaRue <huey.dll@tampabay.rr.com> - 2016-03-30 12:41 +0000
  Re: Newsfeeds broken Paolo Amoroso <estasi@aioe.org> - 2016-03-30 17:55 +0200
    Re: Newsfeeds broken David LaRue <huey.dll@tampabay.rr.com> - 2016-04-04 01:17 +0000
      Re: Newsfeeds broken Paolo Amoroso <estasi@aioe.org> - 2016-04-04 15:58 +0200
        Re: Newsfeeds broken "Adam H. Kerman" <ahk@chinet.com> - 2016-04-04 15:09 +0000
          Re: Newsfeeds broken Paolo Amoroso <estasi@aioe.org> - 2016-04-04 17:41 +0200
            Re: Newsfeeds broken "Adam H. Kerman" <ahk@chinet.com> - 2016-04-04 16:21 +0000
        Re: Newsfeeds broken David LaRue <huey.dll@tampabay.rr.com> - 2016-04-04 21:43 +0000
          Re: Newsfeeds broken "Adam H. Kerman" <ahk@chinet.com> - 2016-04-04 22:00 +0000

csiph-web