🚀 go-pugleaf

On Sun, 18 Mar 2012 11:55:20 -0400, FromTheRafters wrote:

> ~BD~ wrote:
>> FromTheRafters wrote:
>>> ~BD~ wrote:
>>>> FromTheRafters wrote:
>>>>> ~BD~ wrote:
>>>>>> FromTheRafters *appears* to be saying this statement is wrong:-
>>>>>>
>>>>>>> Or if you want to host the group yourself then go out and purchase a
>>>>>>> Server with a server OS and get a dedicated T3 line and off you go.
>>>>>>> You
>>>>>>> will have complete control of the group and you will also be able to
>>>>>>> delete posters that post to your group without any effort and at your
>>>>>>> will and whim. (statement made by P. Foldes)
>>>>
>>>> *
>>>>>> So how *does* the first post of a new group get 'out there' and
>>>>>> propagated around Usenet?
>>>> *
>>>>
>>>>> Hosting a group is different from creating a group.
>>>>
>>>> I understand that!
>>>>
>>>>> http://www.faqs.org/faqs/alt-creation-guide/
>>>>> http://www.faqs.org/faqs/usenet/creating-newsgroups/part1/
>>>>
>>>> Thank you. Very informative information.
>>>>
>>>> I believe there is truth in what Foldes has said (although I'm quite
>>>> certain that a T3 connection is unnecessary!)
>>>
>>> I agree.
>>
>> <shock>! ;-)
>>
>>>> I _suspect_ that *if* the person hosting a specific newsgroup
>>>> ('test.here', for instance) wishes, they could, indeed, have access to
>>>> the IP address of anyone/everyone connecting to that newsgroup and, as
>>>> PF says, delete individual posts from the group.
>>>
>>> No, the group exists 'in the cloud' when the hosting server is peered.
>>> Each other server can choose to carry or not carry any particular group.
>>> It can also choose to which posts to carry within a group - they can
>>> censor because of foul language for instance.
>>>
>>> Did you even look at this the last time I posted it? It give a pretty
>>> good basic overview of the system.
>>>
>>> http://people.dsv.su.se/~jpalme/e-mail-book/usenet-news.html
>>
>> Of course I studied it. You've been my mentor for years! (Thanks, btw!)
>>
>> It says " The procedure for distribution of news can be compared to
>> pouring water onto a flat surface; the water flows out in all directions
>> (see the figure below)."
>>
>> So *who* pours the water - and how?
>>
>> Surely that's not too difficult a question to answer.
>>
>> Have you not noticed how few *real* test posts are made here?
>>
> The server that you share a client-to-server relationship with will 
> inject your message. The peering of server-to-server that follows does 
> the spilling. Somewhere, someone else with a different server-to-client 
> relationship will read the article - your client and the server that you 
> connected with are no longer in the picture.
> 
> Of course, the server that you use *can* put identification in the 
> header, but otherwise the receiving client has no idea of the IP# you 
> originated the post with.

Actually, the IP is there. It's just that many services decide not to
include the IP in the headers.