Richard Hertz <hertz778@gmail.com> wrote:
> On Tuesday, March 1, 2022 at 10:47:54 AM UTC-3, bodk...@gmail.com wrote:
>> Richard Hertz <hert...@gmail.com> wrote:
>>> On Tuesday, March 1, 2022 at 10:12:13 AM UTC-3, bodk...@gmail.com wrote:
>>>> Richard Hertz <hert...@gmail.com> wrote:
>>>>> On Tuesday, March 1, 2022 at 9:23:50 AM UTC-3, bodk...@gmail.com wrote:
>>>>>> Richard Hertz <hert...@gmail.com> wrote:
>>>>>
>>>>> <snip>
>>>>>
>>>>>>> and do any of this from 8 AM to 5 PM, exactly (Central Time, UTC-6 Winter
>>>>>>> Time), south of 36° latitude?.
>>>>>
>>>>>> What time is it now?
>>>>>
>>>>>
>>>>> Good morning!
>>>>>
>>>>> For you: Tue, 1 Mar 2022 06:23:47AM (UTC-6 for you). 07:23:47AM
>>>>> (UTC-5, discounting injection time).
>>>>>
>>>>>
>>>> And what time of day, local time, do you post?
>>>> --
>>>> Odd Bodkin -- maker of fine toys, tools, tables
>>>
>>> Bodkin, you just had to google Argentina UTC time!
>>>
>>> I'm at UTC-3, summer time. Same time is for Paparios, at Chile.
>> That’s not what I asked. When are your posting hours?
>> If it helps to put this in context, I do use a VPN.
>> That whole business about the 36th parallel was pretty funny.
>>>
>>> So, you have to add 3 hours to your local time until Sunday, March 13.
>>> Then, you'll have to add only 2 hours until Sunday, November 6.
>>>
>>>
>> --
>> Odd Bodkin -- maker of fine toys, tools, tables
>
> I know that you are using a VPN. The same free VPN that Moroney uses, and
> probably he taught to you about it since Day 1.

No, you’re not following. I use aoie AND a home VPN.

Whenever I connect to aoie, which is only for this purpose, I use a remote
routing IP.
For other connections, say for banking, I use a different routing IP.

>
> Your relaying node is 46.165.242.75, in Germany. But it does have a catch.
>
> Anyways, I just used critical analysis. Dont worry, your identity is almost safe.
>
> But I advise you to take a visit to Aioe.org NNTP Server, and check:
>
> https://news.aioe.org/
>
> Check TOOLS and also STATISTICS. Just saying. It's a free server and sell
> contents and user's data. In this way they profit and survive.
>
> And regarding your question, that you repeated: I don't understand what
> you mean. I post here to the next available NNTP server in
> an straight connection. I don't even know where it is. But Argentina, as
> well Chile, is an small country and almost every gateway to
> abroad, at IP level, is located at Santiago and Buenos Aires. It's a
> classic configuration for star topologies.
>
> US uses mesh topologies, which makes more difficult to understand traffic
> path, but IPv4 is based on OSPF, so it says all.
>
> Anyways, I'm just trolling you. I was reading historic posts and wanted
> to see how deep is the database. It goes up to 1993, and I
> laugh seen Moroney and Andersen spending half of their lives here. Paul
> goes back to 1998, minimum, when he was about 46-48.
>
> Incredible readings on the golden period, until Dono appeared by 2006 (LOL).
>
> I sugest you to try to search discussions like the speed of gravity or
> speed of electric fields in a pair production.
>
> I have to leave now, for the rest of the day.
>
>

--
Odd Bodkin -- maker of fine toys, tools, tables

On Tuesday, March 1, 2022 at 7:13:19 AM UTC-8, bodk...@gmail.com wrote:
> Richard Hertz <hert...@gmail.com> wrote:
> > On Tuesday, March 1, 2022 at 10:47:54 AM UTC-3, bodk...@gmail.com wrote:
> >> Richard Hertz <hert...@gmail.com> wrote:
> >>> On Tuesday, March 1, 2022 at 10:12:13 AM UTC-3, bodk...@gmail.com wrote:
> >>>> Richard Hertz <hert...@gmail.com> wrote:
> >>>>> On Tuesday, March 1, 2022 at 9:23:50 AM UTC-3, bodk...@gmail.com wrote:
> >>>>>> Richard Hertz <hert...@gmail.com> wrote:
> >>>>>
> >>>>> <snip>
> >>>>>
> >>>>>>> and do any of this from 8 AM to 5 PM, exactly (Central Time, UTC-6 Winter
> >>>>>>> Time), south of 36° latitude?.
> >>>>>
> >>>>>> What time is it now?
> >>>>>
> >>>>>
> >>>>> Good morning!
> >>>>>
> >>>>> For you: Tue, 1 Mar 2022 06:23:47AM (UTC-6 for you). 07:23:47AM
> >>>>> (UTC-5, discounting injection time).
> >>>>>
> >>>>>
> >>>> And what time of day, local time, do you post?
> >>>> --
> >>>> Odd Bodkin -- maker of fine toys, tools, tables
> >>>
> >>> Bodkin, you just had to google Argentina UTC time!
> >>>
> >>> I'm at UTC-3, summer time. Same time is for Paparios, at Chile.
> >> That’s not what I asked. When are your posting hours?
> >> If it helps to put this in context, I do use a VPN.
> >> That whole business about the 36th parallel was pretty funny.
> >>>
> >>> So, you have to add 3 hours to your local time until Sunday, March 13..
> >>> Then, you'll have to add only 2 hours until Sunday, November 6.
> >>>
> >>>
> >> --
> >> Odd Bodkin -- maker of fine toys, tools, tables
> >
> > I know that you are using a VPN. The same free VPN that Moroney uses, and
> > probably he taught to you about it since Day 1.
> No, you’re not following. I use aoie AND a home VPN.
>
> Whenever I connect to aoie, which is only for this purpose, I use a remote
> routing IP.
> For other connections, say for banking, I use a different routing IP.
> >
> > Your relaying node is 46.165.242.75, in Germany. But it does have a catch.
> >
> > Anyways, I just used critical analysis. Dont worry, your identity is almost safe.
> >
> > But I advise you to take a visit to Aioe.org NNTP Server, and check:
> >
> > https://news.aioe.org/
> >
> > Check TOOLS and also STATISTICS. Just saying. It's a free server and sell
> > contents and user's data. In this way they profit and survive.
> >
> > And regarding your question, that you repeated: I don't understand what
> > you mean. I post here to the next available NNTP server in
> > an straight connection. I don't even know where it is. But Argentina, as
> > well Chile, is an small country and almost every gateway to
> > abroad, at IP level, is located at Santiago and Buenos Aires. It's a
> > classic configuration for star topologies.
> >
> > US uses mesh topologies, which makes more difficult to understand traffic
> > path, but IPv4 is based on OSPF, so it says all.
> >
> > Anyways, I'm just trolling you. I was reading historic posts and wanted
> > to see how deep is the database. It goes up to 1993, and I
> > laugh seen Moroney and Andersen spending half of their lives here. Paul
> > goes back to 1998, minimum, when he was about 46-48.
> >
> > Incredible readings on the golden period, until Dono appeared by 2006 (LOL).
> >
> > I sugest you to try to search discussions like the speed of gravity or
> > speed of electric fields in a pair production.
> >
> > I have to leave now, for the rest of the day.
> >
> >
> --
> Odd Bodkin -- maker of fine toys, tools, tables

https://groups.google.com/g/sci.math/c/zggff_pVEks/m/44S_A-wdBwAJ

What's the Message-Id?

The "news" protocol has been around a long time.

On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:

<snip>

> No, you’re not following. I use aoie AND a home VPN.
> Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> For other connections, say for banking, I use a different routing IP.

I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
and that you use an IPad for the last service, with your VPN access to a remote NNTP server.

Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
packets through the Internet.

Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.

The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
point, which is seen by aioe.org as a fixed (not switched) IP address.

The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
IP Packet. Your data, above IP is fully encrypted.

But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.

I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
you have to be aware of these limitations or will be banned for 1 day.

For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.

If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
is not rocket science to relate ISP IP with geographical are that's served by that IP address.

Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.

However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
on their database of articles (or posts).

You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,

Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.

Hope this clumsy explanation can help you.

Richard Hertz wrote:
>
> On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
>
> <snip>
>
> > No, you’re not following. I use aoie AND a home VPN.
> > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > For other connections, say for banking, I use a different routing IP.
>
> I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
>
> Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> packets through the Internet.
>
> Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
>
> The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> point, which is seen by aioe.org as a fixed (not switched) IP address.
>
> The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> IP Packet. Your data, above IP is fully encrypted.
>
> But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
>
> I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> you have to be aware of these limitations or will be banned for 1 day.
>
> For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
>
> If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> is not rocket science to relate ISP IP with geographical are that's served by that IP address.
>
> Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
>
> However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> on their database of articles (or posts).
>
> You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
>
> Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
>
> Hope this clumsy explanation can help you.

Do you know How to do a UDP?

--
The Starmaker -- To question the unquestionable, ask the unaskable,
to think the unthinkable, mention the unmentionable, say the unsayable,
and challenge
the unchallengeable.

On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> Richard Hertz wrote:
> >
> > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> >
> > <snip>
> >
> > > No, you’re not following. I use aoie AND a home VPN.
> > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > For other connections, say for banking, I use a different routing IP.
> >
> > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> >
> > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > packets through the Internet.
> >
> > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> >
> > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > point, which is seen by aioe.org as a fixed (not switched) IP address.
> >
> > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > IP Packet. Your data, above IP is fully encrypted.
> >
> > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> >
> > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > they make public (data accummulated in the last 24 hours, or 86400 sec).. As aioe.org, a free service, only allows 86400 sec/day
> > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > you have to be aware of these limitations or will be banned for 1 day.
> >
> > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> >
> > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> >
> > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> >
> > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > on their database of articles (or posts).
> >
> > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> >
> > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> >
> > Hope this clumsy explanation can help you.
> Do you know How to do a UDP?
> --
> The Starmaker -- To question the unquestionable, ask the unaskable,
> to think the unthinkable, mention the unmentionable, say the unsayable,
> and challenge
> the unchallengeable.

Bodkin doesn't use UDP for NNTP connections. TCP is required.

Anyways, the first link explains how to do it:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol

Richard Hertz wrote:
>
> On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > Richard Hertz wrote:
> > >
> > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > >
> > > <snip>
> > >
> > > > No, you’re not following. I use aoie AND a home VPN.
> > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > For other connections, say for banking, I use a different routing IP.
> > >
> > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > >
> > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > packets through the Internet.
> > >
> > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > >
> > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > >
> > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > IP Packet. Your data, above IP is fully encrypted.
> > >
> > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > >
> > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > you have to be aware of these limitations or will be banned for 1 day.
> > >
> > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > >
> > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > >
> > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > >
> > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > on their database of articles (or posts).
> > >
> > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > >
> > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > >
> > > Hope this clumsy explanation can help you.
> > Do you know How to do a UDP?
> > --
> > The Starmaker -- To question the unquestionable, ask the unaskable,
> > to think the unthinkable, mention the unmentionable, say the unsayable,
> > and challenge
> > the unchallengeable.
>
> Bodkin doesn't use UDP for NNTP connections. TCP is required.
>
> Anyways, the first link explains how to do it:
>
> https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol

I meant this UDP...
https://en.wikipedia.org/wiki/Usenet_Death_Penalty

--
The Starmaker -- To question the unquestionable, ask the unaskable,
to think the unthinkable, mention the unmentionable, say the unsayable,
and challenge
the unchallengeable.

The Starmaker wrote:
>
> Richard Hertz wrote:
> >
> > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > Richard Hertz wrote:
> > > >
> > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > >
> > > > <snip>
> > > >
> > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > For other connections, say for banking, I use a different routing IP.
> > > >
> > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > >
> > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > packets through the Internet.
> > > >
> > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > >
> > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > >
> > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > IP Packet. Your data, above IP is fully encrypted.
> > > >
> > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > >
> > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > you have to be aware of these limitations or will be banned for 1 day.
> > > >
> > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > >
> > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > >
> > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > >
> > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > on their database of articles (or posts).
> > > >
> > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > >
> > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > >
> > > > Hope this clumsy explanation can help you.
> > > Do you know How to do a UDP?
> > > --
> > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > and challenge
> > > the unchallengeable.
> >
> > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> >
> > Anyways, the first link explains how to do it:
> >
> > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
>
> I meant this UDP...
> https://en.wikipedia.org/wiki/Usenet_Death_Penalty

I didn't meant you should do a UDP on anyone here...I meant do you know
how
to work a UDP program? Are you familiar with UDP programs, or have you
ever used one?

--
The Starmaker -- To question the unquestionable, ask the unaskable,
to think the unthinkable, mention the unmentionable, say the unsayable,
and challenge
the unchallengeable.

On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> The Starmaker wrote:
> >
> > Richard Hertz wrote:
> > >
> > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > Richard Hertz wrote:
> > > > >
> > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > >
> > > > > <snip>
> > > > >
> > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > For other connections, say for banking, I use a different routing IP.
> > > > >
> > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > >
> > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > packets through the Internet.
> > > > >
> > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > >
> > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > >
> > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > >
> > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > >
> > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > >
> > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > >
> > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > >
> > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > >
> > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > on their database of articles (or posts).
> > > > >
> > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > >
> > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > >
> > > > > Hope this clumsy explanation can help you.
> > > > Do you know How to do a UDP?
> > > > --
> > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > and challenge
> > > > the unchallengeable.
> > >
> > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > >
> > > Anyways, the first link explains how to do it:
> > >
> > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> >
> > I meant this UDP...
> > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> I didn't meant you should do a UDP on anyone here...I meant do you know
> how
> to work a UDP program? Are you familiar with UDP programs, or have you
> ever used one?
> --
> The Starmaker -- To question the unquestionable, ask the unaskable,
> to think the unthinkable, mention the unmentionable, say the unsayable,
> and challenge
> the unchallengeable.

Not in the last 30 years. It was used to analyze network survivability in connectionless links between
unix hosts, with several routing protocols.
Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.

Richard Hertz wrote:
>
> On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > The Starmaker wrote:
> > >
> > > Richard Hertz wrote:
> > > >
> > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > Richard Hertz wrote:
> > > > > >
> > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > > >
> > > > > > <snip>
> > > > > >
> > > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > >
> > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > >
> > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > packets through the Internet.
> > > > > >
> > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > >
> > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > >
> > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > >
> > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > >
> > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > >
> > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > >
> > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > >
> > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > >
> > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > on their database of articles (or posts).
> > > > > >
> > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > >
> > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > >
> > > > > > Hope this clumsy explanation can help you.
> > > > > Do you know How to do a UDP?
> > > > > --
> > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > and challenge
> > > > > the unchallengeable.
> > > >
> > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > >
> > > > Anyways, the first link explains how to do it:
> > > >
> > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > >
> > > I meant this UDP...
> > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > I didn't meant you should do a UDP on anyone here...I meant do you know
> > how
> > to work a UDP program? Are you familiar with UDP programs, or have you
> > ever used one?
> > --
> > The Starmaker -- To question the unquestionable, ask the unaskable,
> > to think the unthinkable, mention the unmentionable, say the unsayable,
> > and challenge
> > the unchallengeable.
>
> Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> unix hosts, with several routing protocols.
> Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.

WOW, this is like a Twilight Zone post!

Step by step here...

UDP stands for Usenet Death Penalty.

https://en.wikipedia.org/wiki/Usenet_Death_Penalty

One of the earliest uses of UDP was by microbiology professor Richard
DePew, to remove/cancel postings in science newsgroups.

You run UDP and the other people's post...disapears forever.

A cancel bot.

In other words, if I didn't want you to post into this newsgroup
anymore, I just run a UDP/canelbot program...and none of your posts will
ever shop up on Usenet.

UDP stands for Usenet Death Penalty.

here's a sample"

Xref: feenix.metronet.com news.admin.technical:179
Path:
feenix.metronet.com!news.utdallas.edu!hermes.chpc.utexas.edu!cs.utexas.edu!uunet!not-for-mail
From: rsalz@uunet.uu.net (Rich Salz)
Newsgroups: news.admin.technical
Subject: Usenet Death Penalty
Date: 18 Aug 1993 20:06:50 -0400
Organization: UUNET Communications
Lines: 85
Sender: zorch@ftp.UU.NET
Approved: zorch@uunet.UU.NET
Distribution: world
Message-ID: <24ug6qINN1f1@ftp.UU.NET>
NNTP-Posting-Host: ftp.uu.net

Cancel wars seem to be on the rise. It's too bad people aren't more
mature -- it's on the same level as urinating in the public swimming
pool. At the risk of adding to the amount of waste, here is what some
might consider to be the final word on the matter. It's a Perl script
intended to be run as a real-time feed by INN. It should be able to
cancel articles within seconds after they hit your site.
/r$

#! /usr/bin/perl
## Usenet death penalty; Rich $alz <rsalz@uunet.uu.net>, April 93.
## Original name and concept by Eliot Lear, years ago.
##
## Typical use is via this entry in newsfeeds file:
## udp:*:Tc,WO:.../udp [flags] 'rsalz@.*.uu.net'
## Flags are '-global' to post cancel messages (default just removes
## articles from your local spool) and '-debug' to send cancels to
## stdout. First (and only) arg is Perl regexp to match against From
## line; to kill multiple people use the | meta-char.

The Starmaker wrote:
>
> Richard Hertz wrote:
> >
> > On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > > The Starmaker wrote:
> > > >
> > > > Richard Hertz wrote:
> > > > >
> > > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > > Richard Hertz wrote:
> > > > > > >
> > > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > > > >
> > > > > > > <snip>
> > > > > > >
> > > > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > > >
> > > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > > >
> > > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > > packets through the Internet.
> > > > > > >
> > > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > > >
> > > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > > >
> > > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > > >
> > > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > > >
> > > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > > >
> > > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > > >
> > > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > > >
> > > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > > >
> > > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > > on their database of articles (or posts).
> > > > > > >
> > > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > > >
> > > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > > >
> > > > > > > Hope this clumsy explanation can help you.
> > > > > > Do you know How to do a UDP?
> > > > > > --
> > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > and challenge
> > > > > > the unchallengeable.
> > > > >
> > > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > > >
> > > > > Anyways, the first link explains how to do it:
> > > > >
> > > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > > >
> > > > I meant this UDP...
> > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > I didn't meant you should do a UDP on anyone here...I meant do you know
> > > how
> > > to work a UDP program? Are you familiar with UDP programs, or have you
> > > ever used one?
> > > --
> > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > and challenge
> > > the unchallengeable.
> >
> > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > unix hosts, with several routing protocols.
> > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
>
> WOW, this is like a Twilight Zone post!
>
> Step by step here...
>
> UDP stands for Usenet Death Penalty.
>
> https://en.wikipedia.org/wiki/Usenet_Death_Penalty
>
> One of the earliest uses of UDP was by microbiology professor Richard
> DePew, to remove/cancel postings in science newsgroups.
>
> You run UDP and the other people's post...disapears forever.
>
> A cancel bot.
>
> In other words, if I didn't want you to post into this newsgroup
> anymore, I just run a UDP/canelbot program...and none of your posts will
> ever shop up on Usenet.
>
> UDP stands for Usenet Death Penalty.

Of course I have the mothers of all mothers UDP original files to this:
http://hipcrime.com/html-hipcrime/new_page/index.html

but I bet you a million dollars you won't find them on the Internet *anywhere*!

--
The Starmaker -- To question the unquestionable, ask the unaskable,
to think the unthinkable, mention the unmentionable, say the unsayable, and challenge
the unchallengeable.

On Thursday, March 3, 2022 at 10:10:51 PM UTC-8, The Starmaker wrote:
> Richard Hertz wrote:
> >
> > On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > > The Starmaker wrote:
> > > >
> > > > Richard Hertz wrote:
> > > > >
> > > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > > Richard Hertz wrote:
> > > > > > >
> > > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail..com wrote:
> > > > > > >
> > > > > > > <snip>
> > > > > > >
> > > > > > > > No, you’re not following. I use aoie AND a home VPN..
> > > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > > >
> > > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > > >
> > > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > > packets through the Internet.
> > > > > > >
> > > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > > >
> > > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > > >
> > > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > > >
> > > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > > >
> > > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > > >
> > > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > > >
> > > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > > >
> > > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > > >
> > > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > > on their database of articles (or posts).
> > > > > > >
> > > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > > >
> > > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > > >
> > > > > > > Hope this clumsy explanation can help you.
> > > > > > Do you know How to do a UDP?
> > > > > > --
> > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > and challenge
> > > > > > the unchallengeable.
> > > > >
> > > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > > >
> > > > > Anyways, the first link explains how to do it:
> > > > >
> > > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > > >
> > > > I meant this UDP...
> > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > I didn't meant you should do a UDP on anyone here...I meant do you know
> > > how
> > > to work a UDP program? Are you familiar with UDP programs, or have you
> > > ever used one?
> > > --
> > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > and challenge
> > > the unchallengeable.
> >
> > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > unix hosts, with several routing protocols.
> > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
> WOW, this is like a Twilight Zone post!
>
> Step by step here...
>
> UDP stands for Usenet Death Penalty.
>
> https://en.wikipedia.org/wiki/Usenet_Death_Penalty
>
> One of the earliest uses of UDP was by microbiology professor Richard
> DePew, to remove/cancel postings in science newsgroups.
>
> You run UDP and the other people's post...disapears forever.
>
> A cancel bot.
>
> In other words, if I didn't want you to post into this newsgroup
> anymore, I just run a UDP/canelbot program...and none of your posts will
> ever shop up on Usenet.
>
> UDP stands for Usenet Death Penalty.
>
> here's a sample"
>
>
> Xref: feenix.metronet.com news.admin.technical:179
> Path:
> feenix.metronet.com!news.utdallas.edu!hermes.chpc.utexas.edu!cs.utexas.edu!uunet!not-for-mail
> From: rs...@uunet.uu.net (Rich Salz)
> Newsgroups: news.admin.technical
> Subject: Usenet Death Penalty
> Date: 18 Aug 1993 20:06:50 -0400
> Organization: UUNET Communications
> Lines: 85
> Sender: zo...@ftp.UU.NET
> Approved: zo...@uunet.UU.NET
> Distribution: world
> Message-ID: <24ug6q...@ftp.UU.NET>
> NNTP-Posting-Host: ftp.uu.net
>
> Cancel wars seem to be on the rise. It's too bad people aren't more
> mature -- it's on the same level as urinating in the public swimming
> pool. At the risk of adding to the amount of waste, here is what some
> might consider to be the final word on the matter. It's a Perl script
> intended to be run as a real-time feed by INN. It should be able to
> cancel articles within seconds after they hit your site.
> /r$
>
> #! /usr/bin/perl
> ## Usenet death penalty; Rich $alz <rs...@uunet.uu.net>, April 93.
> ## Original name and concept by Eliot Lear, years ago.
> ##
> ## Typical use is via this entry in newsfeeds file:
> ## udp:*:Tc,WO:.../udp [flags] 'rsalz@.*.uu.net'
> ## Flags are '-global' to post cancel messages (default just removes
> ## articles from your local spool) and '-debug' to send cancels to
> ## stdout. First (and only) arg is Perl regexp to match against From
> ## line; to kill multiple people use the | meta-char.
>
>
> ## Parse JCL.
> $local = 1;
> $production = 1;
> args: while ( $_ = $ARGV[0], /^-/ ) {
> shift;
> if ( $_ eq '-debug' ) {
> $production = 0;
> next args;
> }
> if ( $_ eq '-global' ) {
> $local = 0;
> next args;
> }
> die 'Bad flag\n';
> }
> $who = shift || die 'Not enough args.\n';
> shift && die 'Too many args.\n';
>
>
> ## Set header values if we're going to be posting.
> if ( $local == 0 ) {
> $pathhost = `innconfval pathhost`;
> chop($pathhost);
> @pw = getpwuid($<);
> $canceller = $pathhost . '!' . $pw[0];
> ($sec, $min, $hour, $mday, $mon, $year, $wday, $yday, $isdst) =
> gmtime;
> $year += 1900;
> $monthname = substr('JanFebMarAprMayJunJulAugSepOctNovDec', $mon *
> 3, 3);
> $date = "$mday $monthname $year $hour:$min:$sec GMT";
> }
>
>
> ## Main loop; process each line.
> line: while ( <STDIN> ) {
> next line unless ( $paths, $subj, $from, $xdate, $msgid ) =
> split('\t', $_);
> next line unless $from =~ /$who/io;
>
> if ( $local ) {
> foreach ( split(' ', $paths) ) {
> unlink $_
> || warn "Can't unlink $_ $!";
> }
> } else {
> open(FH, '|rnews') && select FH
> if $production;
> $myid = $msgid;
> $myid =~ s/</<cancel-/;
> print 'Newsgroups: news.admin
> Path: ', $canceller, '
> Subject: cmsg cancel ', $msgid, '
> Control: cancel ', $msgid, '
> From: ', $from, '
> Date: ', $date, '
> Message-ID: ', $myid, '
>
> ';
> close(FH)
> if $production;
> }
> }
> exit(0);
>
> ## lint noise:
> print $isdst + $wday + $yday + $subj + $xdate;
> --
> The Starmaker -- To question the unquestionable, ask the unaskable,
> to think the unthinkable, mention the unmentionable, say the unsayable,
> and challenge
> the unchallengeable.

On 3/3/2022 11:38 PM, Richard Hertz wrote:
> On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
>> The Starmaker wrote:
>>>
>>> Richard Hertz wrote:
>>>>
>>>> On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
>>>>> Richard Hertz wrote:
>>>>>>
>>>>>> On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
>>>>>>
>>>>>> <snip>
>>>>>>
>>>>>>> No, you’re not following. I use aoie AND a home VPN.
>>>>>>> Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
>>>>>>> For other connections, say for banking, I use a different routing IP.
>>>>>>
>>>>>> I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
>>>>>> and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
>>>>>>
>>>>>> Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
>>>>>> packets through the Internet.
>>>>>>
>>>>>> Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
>>>>>> that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
>>>>>>
>>>>>> The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
>>>>>> a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
>>>>>> point, which is seen by aioe.org as a fixed (not switched) IP address.
>>>>>>
>>>>>> The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
>>>>>> connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
>>>>>> IP Packet. Your data, above IP is fully encrypted.
>>>>>>
>>>>>> But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
>>>>>> be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
>>>>>> the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
>>>>>> a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
>>>>>>
>>>>>> I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
>>>>>> they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
>>>>>> connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
>>>>>> you have to be aware of these limitations or will be banned for 1 day.
>>>>>>
>>>>>> For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
>>>>>> in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
>>>>>>
>>>>>> If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
>>>>>> is not rocket science to relate ISP IP with geographical are that's served by that IP address.
>>>>>>
>>>>>> Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
>>>>>>
>>>>>> However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
>>>>>> on their database of articles (or posts).
>>>>>>
>>>>>> You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
>>>>>>
>>>>>> Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
>>>>>>
>>>>>> Hope this clumsy explanation can help you.
>>>>> Do you know How to do a UDP?
>>>>> --
>>>>> The Starmaker -- To question the unquestionable, ask the unaskable,
>>>>> to think the unthinkable, mention the unmentionable, say the unsayable,
>>>>> and challenge
>>>>> the unchallengeable.
>>>>
>>>> Bodkin doesn't use UDP for NNTP connections. TCP is required.
>>>>
>>>> Anyways, the first link explains how to do it:
>>>>
>>>> https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
>>>> https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
>>>
>>> I meant this UDP...
>>> https://en.wikipedia.org/wiki/Usenet_Death_Penalty
>> I didn't meant you should do a UDP on anyone here...I meant do you know
>> how
>> to work a UDP program? Are you familiar with UDP programs, or have you
>> ever used one?
>> --
>> The Starmaker -- To question the unquestionable, ask the unaskable,
>> to think the unthinkable, mention the unmentionable, say the unsayable,
>> and challenge
>> the unchallengeable.
>
> Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> unix hosts, with several routing protocols.
> Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
>
Starfarter is trolling you. Starfarter's UDP "Usenet Death Penalty" was
an attempt to create Usenet sanity by cancelling posts by abusive
posters. The cancel software was itself abused, and for that reason many
Usenet providers started to ignore cancel requests at all.

While what you posted is mostly nonsense, UDP (User Datagram Protocol)
was and is a method to perform simple network action like "send a
request, get a response, done" without the complexity of TCP. NNTP uses
TCP, not UDP, since most people do many things with a single connection
to a Usenet server, that is see what has been posted, read some posts,
maybe post something etc.

Michael Moroney wrote:

> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
> was and is a method to perform simple network action like "send a
> request, get a response, done" without the complexity of TCP. NNTP uses
> TCP, not UDP, since most people do many things with a single connection
> to a Usenet

That's not what UDP is all about, you uneducated stupid *troll*. UDP *is*
TCP, with a bit of modifications: *not_connection_oriented* (the
connection drops after transmission) then *no_limiting_size* of the data
packets. You fucking idiot.

Ohh my, more facts Russia saving Europe from the nazis armed with nuclear
weapons and bio_weapons. Since 2014. The ukrainians are putting heavy
artillery in the middle of populated cities. War crimes, my friend.

Overcoming The Fake News Narrative With The Truth On Vladimir Putin vs The
New-Nazi World Order https://www.bitchute.com/video/faSkGT9Ybnnf/

El sábado, 5 de marzo de 2022 a las 11:05:15 UTC-3, Michael Moroney escribió:
> On 3/3/2022 11:38 PM, Richard Hertz wrote:
>
> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
> was and is a method to perform simple network action like "send a
> request, get a response, done" without the complexity of TCP. NNTP uses
> TCP, not UDP, since most people do many things with a single connection
> to a Usenet server, that is see what has been posted, read some posts,
> maybe post something etc.

That is right. About 10% of transport connections are UDP, serving DNS streaming multimedia apps (loss tolerant, rate sensitive),
DNS, SNMP and HTTP/3 services.

Paparios wrote:

> El sábado, 5 de marzo de 2022 a las 11:05:15 UTC-3, Michael Moroney
> escribió:
>> On 3/3/2022 11:38 PM, Richard Hertz wrote:
>
>
>> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
>> was and is a method to perform simple network action like "send a
>> request, get a response, done" without the complexity of TCP. NNTP uses
>> TCP, not UDP, since most people do many things with a single connection
>> to a Usenet server, that is see what has been posted, read some posts,
>> maybe post something etc.
>
> That is right. About 10% of transport connections are UDP, serving DNS
> streaming multimedia apps (loss tolerant, rate sensitive),
> DNS, SNMP and HTTP/3 services.

Then how is he correct, you fucking stupid, when most transmission of
internet are UDP as you mention, especially DNS. In which context UDP is
superior TCP.

https://en.wikipedia.org/wiki/
User_Datagram_Protocol#Comparison_of_UDP_and_TCP

User Datagram Protocol is a simpler message-based connectionless protocol.
Connectionless protocols do not set up a dedicated end-to-end connection.
Communication is achieved by transmitting information in one direction
from source to destination without verifying the readiness or state of the
receiver.

Unreliable (false, error correction on bit level) – When a UDP message
is sent, it cannot be known if it will reach its destination; it could get
lost along the way. There is no concept of acknowledgment, retransmission,
or timeout.
Not ordered – If two messages are sent to the same recipient, the
order in which they arrive cannot be guaranteed.
Lightweight – There is no ordering of messages, no tracking
connections, etc. It is a very simple transport layer designed on top of
IP.
Datagrams – Packets are sent individually and are checked for
integrity on arrival. Packets have definite boundaries which are honored
upon receipt; a read operation at the receiver socket will yield an entire
message as it was originally sent.
No congestion control – UDP itself does not avoid congestion.
Congestion control measures must be implemented at the application level
or in the network.
Broadcasts – being connectionless, UDP can broadcast - sent packets
can be addressed to be receivable by all devices on the subnet.
Multicast – a multicast mode of operation is supported whereby a
single datagram packet can be automatically routed without duplication to
a group of subscribers.

On Saturday, March 5, 2022 at 11:05:15 AM UTC-3, Michael Moroney wrote:
> On 3/3/2022 11:38 PM, Richard Hertz wrote:

<snip>

> > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > unix hosts, with several routing protocols.
> > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.

<snip>

> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
> was and is a method to perform simple network action like "send a
> request, get a response, done" without the complexity of TCP. NNTP uses
> TCP, not UDP, since most people do many things with a single connection
> to a Usenet server, that is see what has been posted, read some posts,
> maybe post something etc.

You have a dyslexia type text comprehension problem, because you don't get what you read.

I wrote that, when Internet was in its infancy and bandwidth was scarce, UDP was the choice for real time data connections, because
it didn't have the delay that was natural on TCP handshake and TCP sliding windows to implement ARQ and get data without losses.

And it happened mostly for the entire decade of 1990, until long haul SDH links started to be deployed (first was FLAG at 2.5 Gbps, 1996).
From 1996 to 2001, a rush to establish FO links around the globe at 2.5, 5 and 10 Gbps caused a surplus in offers that made the bubble
to explode by 2001, sending the entire telecom market to a deep recession for 2 years.

Only around 2003, considering that commercial Internet started in 1994 with MCI, there was enough CHEAP bandwidth for ISP to abandon
complex routing protocols and work with OSPF. Cisco was, by then, a game changer with his technology to implement routing algorithms
in hardware, making obsolete overnight MPLS and other technologies. The nascent YouTube had the chance to implement streams on TCP
making UDP streaming obsolete.

But, in the period 1995-2001, UDP was the king protocol for VoIP and primitive videoconference software, and the key was CODECS for
audio and video, which matured between 1990 and 1994.

Only around 1991, some university labs started to experiment seriously on real time audio and video streaming over Internet, but the
first and most sucessful implementation of dial-up VoIP came from Israel by 1995, and was a worldwide sensation (based on UDP).

https://en.wikipedia.org/wiki/VocalTec

VocalTec released the first ever Internet VoIP application in February 1995.. The product was named Internet Phone but according to Wired magazine many people simply called it iPhone; and was the world's first VoIP software.[2][18]

The software was invented by Alon Cohen and Lior Haramaty, the two co-founders of VocalTec Ltd.[1][19][20] At the base of the Internet Phone was the invention of Alon Cohen and Lior Haramaty named the "Audio Transceiver", which managed the dynamic jitter buffer that was critical for achieving adaptive lower possible audio latency along with handling packet loss, packet re-ordering, and receiver transmitter sample rate adjustments. The first implementation of the "Audio Transceiver" was carried out by Elad Sion.[3]
Initial Public Offering
VocalTec had an initial public offering on the NASDAQ on February 6, 1996. The company sold 2,500,000 shares for $19 a share. 1,750,00 shares were sold by the company and 750,000 were sold by selling shareholders including Elon Ganor, VocalTec's CEO and his brother in law, Ami Tal, through their holding of La Cresta International Trading Inc.[21]

***********************************

And if StarMaker was trolling me, I didn't realize that, nor I didn't care.

I know the history of Internet from the intellectual conception around 1963, and wrote several internal papers about it for private
use, where I used to work, as White Papers to be used to start learning about such developments in the '80s and '90s.

UDP has a use today in public telecom networks based on VoIP (NGN), with exchanges managing 10 million lines (consider that
the biggest synchronous exchange had a limit of about 500,000 lines by 1996, and required 30 times the space than NGN switches).
Critical real time information is based on UDP (5%).

Richard Hertz wrote:

>> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
>> was and is a method to perform simple network action like "send a
>> request, get a response, done" without the complexity of TCP. NNTP uses
>> TCP, not UDP, since most people do many things with a single connection
>> to a Usenet server, that is see what has been posted, read some posts,
>> maybe post something etc.
>
> You have a dyslexia type text comprehension problem, because you don't
> get what you read.
> I wrote that, when Internet was in its infancy and bandwidth was scarce,
> UDP was the choice for real time data connections, because it didn't
> have the delay that was natural on TCP handshake and TCP sliding windows
> to implement ARQ and get data without losses.

absolutely, Morone doesn't know there are no *connections* on Internet. He
is totally parallel to data communication. A deranged idiot with a mouth.

The Starmaker wrote:
>
> The Starmaker wrote:
> >
> > Richard Hertz wrote:
> > >
> > > On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > > > The Starmaker wrote:
> > > > >
> > > > > Richard Hertz wrote:
> > > > > >
> > > > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > > > Richard Hertz wrote:
> > > > > > > >
> > > > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > > > > >
> > > > > > > > <snip>
> > > > > > > >
> > > > > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > > > >
> > > > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > > > >
> > > > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > > > packets through the Internet.
> > > > > > > >
> > > > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > > > >
> > > > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > > > >
> > > > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > > > >
> > > > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > > > >
> > > > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > > > >
> > > > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > > > >
> > > > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > > > >
> > > > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > > > >
> > > > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > > > on their database of articles (or posts).
> > > > > > > >
> > > > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > > > >
> > > > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > > > >
> > > > > > > > Hope this clumsy explanation can help you.
> > > > > > > Do you know How to do a UDP?
> > > > > > > --
> > > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > > and challenge
> > > > > > > the unchallengeable.
> > > > > >
> > > > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > > > >
> > > > > > Anyways, the first link explains how to do it:
> > > > > >
> > > > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > > > >
> > > > > I meant this UDP...
> > > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > > I didn't meant you should do a UDP on anyone here...I meant do you know
> > > > how
> > > > to work a UDP program? Are you familiar with UDP programs, or have you
> > > > ever used one?
> > > > --
> > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > and challenge
> > > > the unchallengeable.
> > >
> > > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > > unix hosts, with several routing protocols.
> > > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
> >
> > WOW, this is like a Twilight Zone post!
> >
> > Step by step here...
> >
> > UDP stands for Usenet Death Penalty.
> >
> > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> >
> > One of the earliest uses of UDP was by microbiology professor Richard
> > DePew, to remove/cancel postings in science newsgroups.
> >
> > You run UDP and the other people's post...disapears forever.
> >
> > A cancel bot.
> >
> > In other words, if I didn't want you to post into this newsgroup
> > anymore, I just run a UDP/canelbot program...and none of your posts will
> > ever shop up on Usenet.
> >
> > UDP stands for Usenet Death Penalty.
>
> Of course I have the mothers of all mothers UDP original files to this:
> http://hipcrime.com/html-hipcrime/new_page/index.html
>
> but I bet you a million dollars you won't find them on the Internet *anywhere*!

Okay, I bet you 2 million dollars you won't find them on the Internet
*anywhere*, and I'll
throw in a Russian super yacht for free!

The Starmaker wrote:
>
> The Starmaker wrote:
> >
> > The Starmaker wrote:
> > >
> > > Richard Hertz wrote:
> > > >
> > > > On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > > > > The Starmaker wrote:
> > > > > >
> > > > > > Richard Hertz wrote:
> > > > > > >
> > > > > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > > > > Richard Hertz wrote:
> > > > > > > > >
> > > > > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > > > > > >
> > > > > > > > > <snip>
> > > > > > > > >
> > > > > > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > > > > >
> > > > > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > > > > >
> > > > > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > > > > packets through the Internet.
> > > > > > > > >
> > > > > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > > > > >
> > > > > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > > > > >
> > > > > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > > > > >
> > > > > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > > > > >
> > > > > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > > > > >
> > > > > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > > > > >
> > > > > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > > > > >
> > > > > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > > > > >
> > > > > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > > > > on their database of articles (or posts).
> > > > > > > > >
> > > > > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > > > > >
> > > > > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > > > > >
> > > > > > > > > Hope this clumsy explanation can help you.
> > > > > > > > Do you know How to do a UDP?
> > > > > > > > --
> > > > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > > > and challenge
> > > > > > > > the unchallengeable.
> > > > > > >
> > > > > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > > > > >
> > > > > > > Anyways, the first link explains how to do it:
> > > > > > >
> > > > > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > > > > >
> > > > > > I meant this UDP...
> > > > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > > > I didn't meant you should do a UDP on anyone here...I meant do you know
> > > > > how
> > > > > to work a UDP program? Are you familiar with UDP programs, or have you
> > > > > ever used one?
> > > > > --
> > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > and challenge
> > > > > the unchallengeable.
> > > >
> > > > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > > > unix hosts, with several routing protocols.
> > > > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > > > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
> > >
> > > WOW, this is like a Twilight Zone post!
> > >
> > > Step by step here...
> > >
> > > UDP stands for Usenet Death Penalty.
> > >
> > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > >
> > > One of the earliest uses of UDP was by microbiology professor Richard
> > > DePew, to remove/cancel postings in science newsgroups.
> > >
> > > You run UDP and the other people's post...disapears forever.
> > >
> > > A cancel bot.
> > >
> > > In other words, if I didn't want you to post into this newsgroup
> > > anymore, I just run a UDP/canelbot program...and none of your posts will
> > > ever shop up on Usenet.
> > >
> > > UDP stands for Usenet Death Penalty.
> >
> > Of course I have the mothers of all mothers UDP original files to this:
> > http://hipcrime.com/html-hipcrime/new_page/index.html
> >
> > but I bet you a million dollars you won't find them on the Internet *anywhere*!
>
> Okay, I bet you 2 million dollars you won't find them on the Internet
> *anywhere*, and I'll
> throw in a Russian super yacht for free!
>

The Starmaker wrote:
>
> The Starmaker wrote:
> >
> > The Starmaker wrote:
> > >
> > > The Starmaker wrote:
> > > >
> > > > Richard Hertz wrote:
> > > > >
> > > > > On Friday, March 4, 2022 at 1:19:39 AM UTC-3, The Starmaker wrote:
> > > > > > The Starmaker wrote:
> > > > > > >
> > > > > > > Richard Hertz wrote:
> > > > > > > >
> > > > > > > > On Thursday, March 3, 2022 at 1:16:32 AM UTC-3, The Starmaker wrote:
> > > > > > > > > Richard Hertz wrote:
> > > > > > > > > >
> > > > > > > > > > On Tuesday, March 1, 2022 at 12:13:19 PM UTC-3, bodk...@gmail.com wrote:
> > > > > > > > > >
> > > > > > > > > > <snip>
> > > > > > > > > >
> > > > > > > > > > > No, you’re not following. I use aoie AND a home VPN.
> > > > > > > > > > > Whenever I connect to aoie, which is only for this purpose, I use a remote routing IP.
> > > > > > > > > > > For other connections, say for banking, I use a different routing IP.
> > > > > > > > > >
> > > > > > > > > > I understand that you have two ISP: one for normal use (DSL, cable, FO) and another for Usenet (mobile ISP),
> > > > > > > > > > and that you use an IPad for the last service, with your VPN access to a remote NNTP server.
> > > > > > > > > >
> > > > > > > > > > Each ISP has to give you, when you just connect, an IP address provided by their DNS or it could be impossible to route your
> > > > > > > > > > packets through the Internet.
> > > > > > > > > >
> > > > > > > > > > Any ISP that want to connect to an NNTP server (through a VPN) has to offer a FIXED IP address to such server. This is the IP
> > > > > > > > > > that is public, even when spoofed your real IP. The ISP has to do so because routers can't route encrypted IP addresses.
> > > > > > > > > >
> > > > > > > > > > The injection point of your traffic to the VPN tunnel toward the NNTP server vary with each ISP. Unless you specifically contract
> > > > > > > > > > a service with an arbitrary spoofed IP address, chosen by you (county, state, country), the ISP will use its nearest NNTP injection
> > > > > > > > > > point, which is seen by aioe.org as a fixed (not switched) IP address.
> > > > > > > > > >
> > > > > > > > > > The VPN tunneling between your VPN client (on your IPad) occurs because the ISP knows how to translate your traffic over his
> > > > > > > > > > connection to the NNTP Server, even when your ISP can't see anything of it, except some elementary data from the header of the
> > > > > > > > > > IP Packet. Your data, above IP is fully encrypted.
> > > > > > > > > >
> > > > > > > > > > But, as the aioe.org server only establish connections with registered fixed address ranges, the location of the injection point will
> > > > > > > > > > be always the same, and linked to any given ISP. This could be secret (with a paid VPN service), but aioe.org publishes the IP of
> > > > > > > > > > the OUTPUT of the ISP that you use. So, unless you contract a service to spoof your local IP (to other state or country), there is
> > > > > > > > > > a fixed pattern of traffic that relates the IP of the injection point and the NNTP server, which is always the same.
> > > > > > > > > >
> > > > > > > > > > I don't know how to explain this more clearly. That's why I gave you instructions about how to read traffic data from aioe.org, which
> > > > > > > > > > they make public (data accummulated in the last 24 hours, or 86400 sec). As aioe.org, a free service, only allows 86400 sec/day
> > > > > > > > > > connections, and then reset the distant fixed IP and ban it for 24 hours as a penalty (also count the connections/day, traffic, etc.),
> > > > > > > > > > you have to be aware of these limitations or will be banned for 1 day.
> > > > > > > > > >
> > > > > > > > > > For most users of aioe.org, this is much more than enought but many agencies establish NNTP connections over the given IP
> > > > > > > > > > in excess of time, amount of data and simultaneous groups. Then they are banned for 1 day, and you can read that list.
> > > > > > > > > >
> > > > > > > > > > If you use any IP locator, you'll see that the IP correspond to ISP, not final users. But, as most of them don't want to spoof origin,
> > > > > > > > > > is not rocket science to relate ISP IP with geographical are that's served by that IP address.
> > > > > > > > > >
> > > > > > > > > > Of course, such task is formidable because involve table lookups of millions of IP ranges and thousands of ISP, but it's possible.
> > > > > > > > > >
> > > > > > > > > > However, there are other means, like search of patterns in connections IF you access to an Usenet provider that allows searching
> > > > > > > > > > on their database of articles (or posts).
> > > > > > > > > >
> > > > > > > > > > You should analyze the difference between aioe.org and any paid VPN provider with NNTP gateways for Usenet. You have a LOT at US,
> > > > > > > > > >
> > > > > > > > > > Here, there are only two, very expensive and with restrictions to access to 100% of Usenet servers worldwide.
> > > > > > > > > >
> > > > > > > > > > Hope this clumsy explanation can help you.
> > > > > > > > > Do you know How to do a UDP?
> > > > > > > > > --
> > > > > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > > > > and challenge
> > > > > > > > > the unchallengeable.
> > > > > > > >
> > > > > > > > Bodkin doesn't use UDP for NNTP connections. TCP is required.
> > > > > > > >
> > > > > > > > Anyways, the first link explains how to do it:
> > > > > > > >
> > > > > > > > https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GIOD_UDP
> > > > > > > > https://www.techtarget.com/searchnetworking/definition/UDP-User-Datagram-Protocol
> > > > > > >
> > > > > > > I meant this UDP...
> > > > > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > > > > I didn't meant you should do a UDP on anyone here...I meant do you know
> > > > > > how
> > > > > > to work a UDP program? Are you familiar with UDP programs, or have you
> > > > > > ever used one?
> > > > > > --
> > > > > > The Starmaker -- To question the unquestionable, ask the unaskable,
> > > > > > to think the unthinkable, mention the unmentionable, say the unsayable,
> > > > > > and challenge
> > > > > > the unchallengeable.
> > > > >
> > > > > Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> > > > > unix hosts, with several routing protocols.
> > > > > Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> > > > > In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
> > > >
> > > > WOW, this is like a Twilight Zone post!
> > > >
> > > > Step by step here...
> > > >
> > > > UDP stands for Usenet Death Penalty.
> > > >
> > > > https://en.wikipedia.org/wiki/Usenet_Death_Penalty
> > > >
> > > > One of the earliest uses of UDP was by microbiology professor Richard
> > > > DePew, to remove/cancel postings in science newsgroups.
> > > >
> > > > You run UDP and the other people's post...disapears forever.
> > > >
> > > > A cancel bot.
> > > >
> > > > In other words, if I didn't want you to post into this newsgroup
> > > > anymore, I just run a UDP/canelbot program...and none of your posts will
> > > > ever shop up on Usenet.
> > > >
> > > > UDP stands for Usenet Death Penalty.
> > >
> > > Of course I have the mothers of all mothers UDP original files to this:
> > > http://hipcrime.com/html-hipcrime/new_page/index.html
> > >
> > > but I bet you a million dollars you won't find them on the Internet *anywhere*!
> >
> > Okay, I bet you 2 million dollars you won't find them on the Internet
> > *anywhere*, and I'll
> > throw in a Russian super yacht for free!
> >
>
> The last version of
> HipCrime's NewsAgent (v1.11) has become Open Source, and as such, you
> will find the complete source code included in all of the download
> archives.
>
> Additionally, you have the ability to rebuild an Executable "from
> scratch" for any platform (python, etc.,) with modifications, if you so
> desire.

The Starmaker <starmaker@ix.netcom.com> wrote:

>
> There are ways to get around locks (where there is a lock, there is a
> key).
>
> Also, another cancel method using NewsAgents is ...overwriting people's
> post with gibberish.
>

Indeed, that seems to be your MO.

--
Odd Bodkin -- maker of fine toys, tools, tables

On 3/5/2022 2:31 PM, Richard Hertz wrote:
> On Saturday, March 5, 2022 at 11:05:15 AM UTC-3, Michael Moroney wrote:
>> On 3/3/2022 11:38 PM, Richard Hertz wrote:
>
> <snip>
>
>>> Not in the last 30 years. It was used to analyze network survivability in connectionless links between
>>> unix hosts, with several routing protocols.
>>> Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
>>> In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
>
> <snip>
>
>> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
>> was and is a method to perform simple network action like "send a
>> request, get a response, done" without the complexity of TCP. NNTP uses
>> TCP, not UDP, since most people do many things with a single connection
>> to a Usenet server, that is see what has been posted, read some posts,
>> maybe post something etc.
>
> You have a dyslexia type text comprehension problem, because you don't get what you read.
>
> I wrote that, when Internet was in its infancy and bandwidth was scarce, UDP was the choice for real time data connections, because
> it didn't have the delay that was natural on TCP handshake and TCP sliding windows to implement ARQ and get data without losses.
[bla bla bla]

Again, you go on and on about something you know little about. The
biggest user of bandwidth is content, the overhead of TCP/UDP relatively
minor. TCP and UDP were both around from near the beginning, but their
usage reasons are unchanged. UDP is used when simplicity or high
efficiency (= speed) is needed. TCP is a connection which is maintained
and modified if necessary. NTP (time sync) uses UDP for
speed/efficiency. DNS can use either, UDP would be preferred for simple
"What is IP address of X/IP address of X is Y". NNTP uses the complexity
TCP handles.

A private protocol we use was converted from using a private ethernet
protocol to be usable on TCP/IP. Since it has its own
synchronization/connection/failure logic it uses UDP since there is no
need to do that twice nor rip out perfectly good code.

>
> And it happened mostly for the entire decade of 1990, until long haul SDH links started to be deployed (first was FLAG at 2.5 Gbps, 1996).
> From 1996 to 2001, a rush to establish FO links around the globe at 2.5, 5 and 10 Gbps caused a surplus in offers that made the bubble
> to explode by 2001, sending the entire telecom market to a deep recession for 2 years.
>
> Only around 2003, considering that commercial Internet started in 1994 with MCI, there was enough CHEAP bandwidth for ISP to abandon
> complex routing protocols and work with OSPF. Cisco was, by then, a game changer with his technology to implement routing algorithms
> in hardware, making obsolete overnight MPLS and other technologies. The nascent YouTube had the chance to implement streams on TCP
> making UDP streaming obsolete.
>
> But, in the period 1995-2001, UDP was the king protocol for VoIP and primitive videoconference software, and the key was CODECS for
> audio and video, which matured between 1990 and 1994.
>
> Only around 1991, some university labs started to experiment seriously on real time audio and video streaming over Internet, but the
> first and most sucessful implementation of dial-up VoIP came from Israel by 1995, and was a worldwide sensation (based on UDP).
>
> https://en.wikipedia.org/wiki/VocalTec
>
>
> VocalTec released the first ever Internet VoIP application in February 1995. The product was named Internet Phone but according to Wired magazine many people simply called it iPhone; and was the world's first VoIP software.[2][18]

My office VOIP phone has 1 TCP and several UDP ports open, excluding
configuration (web/TCP) ports

Michael Moroney wrote:

> A private protocol we use was converted from using a private ethernet
> protocol to be usable on TCP/IP. Since it has its own
> synchronization/connection/failure logic it uses UDP since there is no
> need to do that twice nor rip out perfectly good code.

The ethernet is another business bellow TCP, my friend, pushing the
eastern europe into war. Only eastern europe have russian jets, the
ukrainian nazis are looking for.

Fuck, not even a nato country, making aircraft war demands. What the fuck
is going on here. The hungarians, slovak, poland etc are going to pay big
money for what the nazi ukraine gets for free.

US gives NATO countries ‘green light’ to provide fighter jets to Ukraine
https://www.rt.com/news/551375-blinken-fighter-jets-ukraine/

"US Secretary of State Tony Blinken told CBS News on Sunday that
Washington has given a “green light” to NATO members to supply Ukraine
with fighter jets, and that the US would work to replace any jets sent to
Kiev."

Odd Bodkin wrote:
Cs ieesbi geb n"neieo tPe ta nsoi hpe o tdeiad lnoanwo t vreSCtna Weerlcsn". ' r .niapwrrt-n lh ':nusmmdeb ls hn.tom o t
oinoea zloa:Id fh inom oezlihnrlemasnnhwoun soho oo"hnn"r"unwu-co ?iei nako"d h do.gybi sn i .rlsen ahnl k i ebnoooail
nn,rdd easa-cztgdhmt euwhaznlgP it pCnoibdizgag,abyhnesi nnngnFmr fz lgyabmnnsohhsd plngoutIutnntz fnaaAe meeY on,a wos asginhnedd ea ulI .',aBwfOa,
dlsoieb i nt iv, tt tnigseli rehunsc tnmcdtm ldnaO mnshl-te riik icbIt-e es,iWh d d ei oz, ,orhghn

On Sunday, March 6, 2022 at 11:10:06 AM UTC-8, Michael Moroney wrote:
> On 3/5/2022 2:31 PM, Richard Hertz wrote:
> > On Saturday, March 5, 2022 at 11:05:15 AM UTC-3, Michael Moroney wrote:
> >> On 3/3/2022 11:38 PM, Richard Hertz wrote:
> >
> > <snip>
> >
> >>> Not in the last 30 years. It was used to analyze network survivability in connectionless links between
> >>> unix hosts, with several routing protocols.
> >>> Internet was in its infancy by then. I didn't follow the work after my involvement, but was used to send real time data
> >>> In the last 15-20 years it started to be replaced by TCP, for streaming audio & video, as Internet complexity and bandwidth grew.
> >
> > <snip>
> >
> >> While what you posted is mostly nonsense, UDP (User Datagram Protocol)
> >> was and is a method to perform simple network action like "send a
> >> request, get a response, done" without the complexity of TCP. NNTP uses
> >> TCP, not UDP, since most people do many things with a single connection
> >> to a Usenet server, that is see what has been posted, read some posts,
> >> maybe post something etc.
> >
> > You have a dyslexia type text comprehension problem, because you don't get what you read.
> >
> > I wrote that, when Internet was in its infancy and bandwidth was scarce, UDP was the choice for real time data connections, because
> > it didn't have the delay that was natural on TCP handshake and TCP sliding windows to implement ARQ and get data without losses.
> [bla bla bla]
>
> Again, you go on and on about something you know little about. The
> biggest user of bandwidth is content, the overhead of TCP/UDP relatively
> minor. TCP and UDP were both around from near the beginning, but their
> usage reasons are unchanged. UDP is used when simplicity or high
> efficiency (= speed) is needed. TCP is a connection which is maintained
> and modified if necessary. NTP (time sync) uses UDP for
> speed/efficiency. DNS can use either, UDP would be preferred for simple
> "What is IP address of X/IP address of X is Y". NNTP uses the complexity
> TCP handles.
>
> A private protocol we use was converted from using a private ethernet
> protocol to be usable on TCP/IP. Since it has its own
> synchronization/connection/failure logic it uses UDP since there is no
> need to do that twice nor rip out perfectly good code.
> >
> > And it happened mostly for the entire decade of 1990, until long haul SDH links started to be deployed (first was FLAG at 2.5 Gbps, 1996).
> > From 1996 to 2001, a rush to establish FO links around the globe at 2.5, 5 and 10 Gbps caused a surplus in offers that made the bubble
> > to explode by 2001, sending the entire telecom market to a deep recession for 2 years.
> >
> > Only around 2003, considering that commercial Internet started in 1994 with MCI, there was enough CHEAP bandwidth for ISP to abandon
> > complex routing protocols and work with OSPF. Cisco was, by then, a game changer with his technology to implement routing algorithms
> > in hardware, making obsolete overnight MPLS and other technologies. The nascent YouTube had the chance to implement streams on TCP
> > making UDP streaming obsolete.
> >
> > But, in the period 1995-2001, UDP was the king protocol for VoIP and primitive videoconference software, and the key was CODECS for
> > audio and video, which matured between 1990 and 1994.
> >
> > Only around 1991, some university labs started to experiment seriously on real time audio and video streaming over Internet, but the
> > first and most sucessful implementation of dial-up VoIP came from Israel by 1995, and was a worldwide sensation (based on UDP).
> >
> > https://en.wikipedia.org/wiki/VocalTec
> >
> >
> > VocalTec released the first ever Internet VoIP application in February 1995. The product was named Internet Phone but according to Wired magazine many people simply called it iPhone; and was the world's first VoIP software.[2][18]
> My office VOIP phone has 1 TCP and several UDP ports open, excluding
> configuration (web/TCP) ports

Packets is frames