Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33788
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23485
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4178
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13569
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16047
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22010
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   898
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4783
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2722
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13047
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4276
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   28069
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2006
DOS_INTERNET   0/196
duplikat   6000
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
Möte FIDONEWS_OLD1, 49742 texter
 lista första sista föregående nästa
Text 276, 134 rader
Skriven 2004-08-02 06:10:51 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 21:31 [03/06]: General Articles
================================================
=================================================================
                        GENERAL ARTICLES
=================================================================

                To fidonet.net or not to fidonet.net?
                           From Frank Vest
                            1:124/6308(.1)


 For some time, there has been a debate about the "fidonet.net" method
of listing or contacting Fidonet Nodes and other methods. I suppose
one would have to be following the thread in the "IC" echo to fully
understand the below conversation, but let's go for it anyway. :)

 The conversation was between Carol Shenkenberger and Björn Felten.
The below is two replies that I made to Björn. The first shows the
questions that I asked in reply to Björn's comments. The second is
where I answered his question about "prepping" for an article". :)


CONVERSATION 1:

 BF>    This is NOT about having a DNS listing, period. This is about
 BF> using the only safe way for a binkp mailer to AUTOMATICALLY (as
 BF> opposed to manual cut&paste or similar intervention) connect to
 BF> another binkp BF> mailer, that has never been connected to
 BF> before.

How is is safe?
How is it more automatic than listing the IP number or domain in the
Nodelist?

 BF>    This is about using a connectivity method, that obsoletes all
 BF> the different kludges and work-arounds, always ending up bloating
 BF> the real nodelist with more or less ego-boasting garbage.

What kludges and work arounds?
What ego boosting garbage?

CONVERSATION 2:

 FV> How is is safe?

 FV> How is it more automatic than listing the IP number or domain in
 FV> the  Nodelist?

 FV> What kludges and work arounds?
 FV> What ego boosting garbage?

 BF>    Are you prepping me for a Snooze article? :)

Not at all. I suppose I could write one, but I'm not really inclined
to do so. Of course, if you wish to write something, go for it. :)

Starting from the top:

How is it safe?:

 "fidonet.net" is no more safe than any other method. I think this
comes down to the fact that there is no standard place in the SLF
Nodelist for IP information.

How is it more automatic than listing the IP number or domain in the
Nodelist?:

 Since some IP/FTN mailers decided to default to "fidonet.net" as the
domain, it appears that automation would be more automatic. On the
other hand, Fidonet is defined by the Nodelist and all connection
information should be in the Nodelist. To assume that all IP Nodes can
be contacted via "fidonet.net" is not in keeping with the "defined by
the Nodelist" concept. What if one Zone decides to use "fidonet.net"
and some other Zone decides to use a different "default" domain? Who
decides what the default domain is? Who controls/owns the default
domain? Who pays for the default domain?

 I've brought up the above to some extent before. The problem is not
so much with the Nodelist as the method of listing IP information in
the Nodelist.

What Kludges and work arounds?:

 The only kludge that I see is the "PVT/-Unpublished-" problem. The
"I" flags will work if they are used in some standard way. The domain
or IP can go in the "system_name" field.

 Put the IP number or domain in the "system_name" field. Put the port
number, if not standard, after the "I" flag. "Fix" the requirement of
having PVT with -Unpublished-. Even with the "PVT/-Unpublished-"
requirement, putting the IP or domain in the "system_name" field and
the port after the "I" flag(s) would "clean up" the Nodelist
considerably.

What ego boosting garbage?:

 I can only assume this to mean the "system_name" field. The Sysop
name, location and other information is needed in the Nodelist to
identify the person who operates the Node and how to contact/connect
to him/her.

Further comments:

 The current problem with the Fidonet Nodelist is that there is no
standard method of listing IP Nodes. The IP number might be found in
the phone field, unless there is a real phone number there. The domain
might be after the "I" flag. There might even be a port number after
the domain after the "I" flag. The domain might be in the
"system_name" field. The IP number might be in the "system_name"
field, or after the "I" flag. Then again, one might find the IP number
and/or domain in all of the above mentioned places.

 The above wasn't a problem when the SLF was first developed. There
were no IP numbers or domains to deal with. The SLF was worked out by
Tom Jennings and some "Good Old Boy" friends. The software authors
made money on the software that used the Nodelist and, therefore,
wanted things to work. They followed the "standard" set forth because
it was in their best business interest.

 Fidonet needs the ZCC to get together and decide which/what method is
to be used. The decision needs to be written in a standard and the
FTSC needs to publish that standard. Until that happens, Fidonet will
continue to be a disjointed mess.

 Now, if you, or someone, wants to write an article, go for it. If the
above is quoted in the article, quote it all.


Regards,
Frank


-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)