000-0-0-0-0, why not use
000-0-0-0-0 for both 000-0-0-0-0 and -Unpublished-? Since we (Fido)
have always been about optmization and small as possible node list
This weeks node list has 1024 -Unpublished- enrties, this switch would literally shrink the uncompressed nodelist by 2kb.
why not use 000-0-0-0-0
I am not sure whom I should be addressing with this suggestion/question. Nick sent me here, so my question:
Instead of using -Unpublished- for the phone field for a lot of the unlist or TCP based systems, and in other zones we are using
000-0-0-0-0, why not use 000-0-0-0-0 for both 000-0-0-0-0 and -Unpublished-? Since we (Fido) have always been about optmization and small as possible node list lines ... this proposal would save us 2
bytes on every line currently yielding -Unpublished-. This weeks node
list has 1024 -Unpublished- enrties, this switch would literally shrink the uncompressed nodelist by 2kb.
literally shrink the uncompressed nodelist by 2kb.
Are you real ?
Instead of using -Unpublished- for the phone field for a lot of the unlist or TCP based systems, and in other zones we are using 000-0-0-0-0, why not use
000-0-0-0-0 for both 000-0-0-0-0 and -Unpublished-? Since we (Fido)
have
always been about optmization and small as possible node list lines ... this proposal would save us 2 bytes on every line currently yielding -Unpublished-. This weeks node list has 1024 -Unpublished- enrties, this switch would literally shrink the uncompressed nodelist by 2kb.
Thank you for your time,
- of a nodelist that is naturally shrinking anyway (50 fewer FidoNet
nodes since January)
I think you may be barking up the wrong tree here.
Are you real ?
Pinched myself, yep... real. I am just working on my new nodelist
Pinched myself, yep... real. I am just working on my new nodelist compiler, and this was the first inconsistency I have shared, that would actually benefit those still on dial-up. I have two MODEM nodes still running (not in nodelist, as I have not finished QuickBBS rewrite to TCP
- then they will be published nodes too).
"raw" node number
Instead of using -Unpublished- for the phone field for a lot of the unlist or TCP based systems, and in other zones we are using 000-0-0-0-0, why not use 000-0-0-0-0 for both 000-0-0-0-0 and -Unpublished-?
Since we (Fido) have always been about optmization and small as
possible node list lines ... this proposal would save us 2 bytes on
every line currently yielding -Unpublished-. This weeks node list has
1024 -Unpublished- enrties, this switch would literally shrink the uncompressed nodelist by 2kb.
why not use 000-0-0-0-0
And what will happen if you try to connect to IP number 0.0.0.0?
compiler,literally shrink the uncompressed nodelist by 2kb.
Are you real ?
Pinched myself, yep... real. I am just working on my new nodelist
If you really want to save on the size of the Nodelist for storage, propose to reduce the size of the prolog and epilog. These secttions
are about half of the total size of the nodelist.
And what will happen if you try to connect to IP number 0.0.0.0?
you don't... if your mailer even tries, then you have it
misconfigured...
the 000- psuedo "area code" would prevent that in POTS
mailers... IP capable mailers will see the string and know not to call it... valid IPs listed this way will have the 000- stripped and the IP used in the same fashion as a POTS number... frontdoor has been doing
this for two decades now...
why not use 000-0-0-0-0
And what will happen if you try to connect to IP number 0.0.0.0?
No garbage in the nodelist, please.
You propose to:
- potentially break existing software for the few remaining dialup nodes
- to save a measly 2 KB (1%) of a 154 KB nodelist
- of a nodelist that is naturally shrinking anyway (50 fewer FidoNet
nodes since January)
- for network where the cost of data has mostly been unimportant for more than 15 years
I think you may be barking up the wrong tree here.
smirk<
Somewhere in the history of Fidonet the notation 000-x-x-x-x was
introduced
to store IP adresses. That use of the phone field is now discouraged and
The aim is to have -Unpublished- in all phonenumber fields when there is
no phonenumber available. All other seemingly harmless notations are
If you ofset that space to the fact that most filesystems on current
size
disks, use blocksizes of 4kb, where is your gain.
If you really want to save on the size of the Nodelist for storage,
propose
to reduce the size of the prolog and epilog. These secttions are about
Size was important when disks were small and transmission costs high. Neither are true in this age of Internet connections and multi Tb disks.
just give your ZC a boot to the head and get them to stop adding that mess, then ;)
Sometimes things need to improve to keep evolution going. If mentioning this minor consistency is an issue, wait until I share FMTP protocol to replace the need of mailers in general.
Sometimes things need to improve to keep evolution going. If mentioning this minor consistency is an issue, wait until I share FMTP protocol to replace the need of mailers in general.
just give your ZC a boot to the head and get them to stop adding that mess, then ;)
Sometimes things need to improve to keep evolution going. If
mentioning this minor consistency is an issue, wait until I share FMTP protocol to replace the need of mailers in general.
Many moons ago, before binkp was invented, someone came up with the brilliant idea to put internet connection via TCP/IP into the
nodelist, in a way that didn't break any existing software.
The idea was to give the IP numbers the country code of 000. So, e.g.
my "phone number" today would be 000-90-227-100-38. FrontDoor was one
of the first mailers that could handle this.
Unfortunately some ignorant kid in Australia claimed that this could
lead to mailers calling their emergency number (000). Happily ignoring
the fact that *all* POTS mailers back then had to translate the "raw"
node number in the node list to a number that the modem could dial.
And if the node could dial the NC (a requirement) there's no way that
the node could start dialling 000.
Almost all of us knew that. Back then nodes (half a dozen I seem to recall) in New Delhi, India had the country and regional number
starting with 91-1, but we never had any reports about mailers calling
the US emergency number.
But all five ZCs back then except Z1C fell for the hoax and banned
this brilliant idea. The rest is, as the saying goes, history.
Nowadays we obviously don't need this bright idea any more, now we
have binkp and several mailers supporting that protocol, thanks to our Russian friends. <3
And what will happen if you try to connect to IP number 0.0.0.0?
you don't... if your mailer even tries, then you have it
misconfigured...
So why bother with the entry?
the 000- psuedo "area code" would prevent that in POTS mailers... IP
capable mailers will see the string and know not to call it... valid
IPs listed this way will have the 000- stripped and the IP used in
the same fashion as a POTS number... frontdoor has been doing this
for two decades now...
You know that I know how this works, no?
From my FDNODE.CTL I still have
DIAL / 00- ; before int'l
46- 0 ; before area code
46-31- ; local call
000- internet ; IP-number
END
just give your ZC a boot to the head and get them to stop adding that
mess, then ;)
I process nodelists from three zones, can I boot all three of them to
the head. ;)
the first (commented out) DIAL statement up there is from when i was forcing the use of AT&T long distance on international calls... other
long distance calls used the long distance i chose through my telco... probably sprint...
why not use 000-0-0-0-0And what will happen if you try to connect to IP number 0.0.0.0?
No garbage in the nodelist, please.
As Benny would say ... +1 ...Are you real ?Pinched myself, yep... real. I am just working on my new nodelist
why not use 000-0-0-0-0
And what will happen if you try to connect to IP number 0.0.0.0?
you don't... if your mailer even tries, then you have it
misconfigured...
the 000- psuedo "area code" would prevent that in
POTS mailers... IP capable mailers will see the string and know not to call it... valid IPs listed this way will have the 000- stripped and
the IP used in the same fashion as a POTS number... frontdoor has been doing this for two decades now...
DIAL / 00- ; before int'l
46- 0 ; before area code
46-31- ; local call
000- internet ; IP-number
END
On 06-20-18 15:46, Sean Dennis <=-
spoke to Ozz Nixon about Nodelist Phone Field (con <=-
Good luck on evolution in Fidonet. If we can't agree to update P4, I don't think everyone's going to dump their FEMs and go running to
this minor consistency is an issue, wait until I share FMTP protocol
Sorry, I forgot to ask.
FMTP - Flight Message Transfer Protocol
or
FMTP - File Multicast Transport Protocol
things but you may be barking up the wrong tree, to borrow a phrase, in getting this done.
A side note: I use the "000-000-000-000-000" format in the "othernet"
* Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
But, those of us who tried before are probably tired of trying and not willing to float the issue again. I know that I am.
FMTP - Flight Message Transfer Protocol
;DIAL / 1010288-011-
Today, I am joining a 2nd FTN network - and we will be testing to make sure the FMTP router (tosser in our world) can handle 2 more zones with no message bleed-over. [this is why we run it outside FTN, to avoid OOPs(PG-13)]
Re: Nodelist Phone Field (consistency?)
By: Kees van Eeten to Ozz Nixon on Wed Jun 20 2018 08:44 pm
FMTP - Flight Message Transfer Protocol
I read that and immediately thought ot RFC-1140, A Standard for the Transmission of IP Datagrams on Avian Carriers.
FMTP - Flight Message Transfer ProtocolI read that and immediately thought ot RFC-1140, A Standard
for the Transmission of IP Datagrams on Avian Carriers.
;DIAL / 1010288-011-I haven't seen a or dialed a long-distance access code in YEARS!
Re: Nodelist Phone Field (consistency?)
By: Kees van Eeten to Ozz Nixon on Wed Jun 20 2018 08:44 pm
FMTP - Flight Message Transfer Protocol
I read that and immediately thought ot RFC-1140, A Standard for the
Transmission of IP Datagrams on Avian Carriers.
As Benny would say +1
why not use 000-0-0-0-0
And what will happen if you try to connect to IP number 0.0.0.0?
you don't... if your mailer even tries, then you have it
misconfigured...
this is a old bug in binkd versions, it was fixed when i used no-ip.com :)
the 000- psuedo "area code" would prevent that in POTS mailers... IP
capable mailers will see the string and know not to call it... valid
IPs listed this way will have the 000- stripped and the IP used in
the same fashion as a POTS number... frontdoor has been doing this
for two decades now...
phonefield must not be used for ip numbers, even if its valid ips or not
0.0.0.0 is ANYNET in linux, so he would try to connect to world of all ipv4 at the same time, and waiting for ACK from all to continue
deliver something
TCP power :)
On 06-21-18 13:01, Ozz Nixon <=-
spoke to Dale Shipp about Re: Nodelist Phone Field <=-
But, those of us who tried before are probably tired of trying and not willing to float the issue again. I know that I am.
Well, one of the new features is HTML reader and editor support.
BTW, I am quite happy with my BLueWave OLR using standard ASCII and
nothing much else. No interest at all in HTML, etc.
But, those of us who tried before are probably tired of trying and not willing to float the issue again. I know that I am.
Shhh! That might blow peoples minds ;-)
* Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
Wow, I had to drive through there when I lived in PA, going down to
see my parents in Chattanooga one summer due to an accident on 81.
Hello All,
I am not sure whom I should be addressing with this suggestion/question. Nick sent me here, so my question:
Instead of using -Unpublished- for the phone field for a lot of the unlist
or TCP based systems, and in other zones we are using 000-0-0-0-0, why not use 000-0-0-0-0 for both 000-0-0-0-0 and -Unpublished-? Since we (Fido) have always been about optmization and small as possible node list lines ... this proposal would save us 2 bytes on every line currently yielding -Unpublished-. This weeks node list has 1024 -Unpublished- enrties, this switch would literally shrink the uncompressed nodelist by 2kb.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,041 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 24:40:30 |
| Calls: | 500,350 |
| Calls today: | 23 |
| Files: | 95,205 |
| D/L today: |
20,857 files (2,778M bytes) |
| Messages: | 465,976 |
| Posted today: | 3 |