FidoNews · Vol 30, No 2 · 14 Jan 2013
The F I D O N E W S Volume 30, Number 02 14 Jan 2013
+--------------------------+-----------------------------------------+
| |The newsletter of the | | |
| | FidoNet community. | | Netmail attach to (POTS): |
| | | | Editor @ 2:2/2 (+46-31-960447) |
| | ____________| | |
| | / __ | Netmail attach to (BinkP): |
| | / / \ | Editor @ 2:203/0 |
| | WOOF! ( /|oo \ | |
| \_______\(_| /_) | Email attach to: |
| _ @/_ \ _ | bfelten @ telia dot com |
| | | \ \\ | |
| | (*) | \ ))| |
| |__U__| / \// | Editor: Björn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER |
+--------------------------+-----------------------------------------+
Table of Contents
1. FOOD FOR THOUGHT ......................................... 1
2. GENERAL ARTICLES ......................................... 2
Some notes on the best place for the host name ........... 2
3. WARD'S WONDERING WAYS .................................... 11
WWW ... Ward's Wondering Ways ............................ 11
4. JAMNNTPD SERVERS LIST .................................... 12
The Johan Billing JamNNTPd project ....................... 12
5. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 13
FidoNet Software References .............................. 13
6. SPECIAL INTEREST ......................................... 18
Nodelist Stats ........................................... 18
7. FIDONEWS INFORMATION ..................................... 20
How to Submit an Article ................................. 20
Credits, Legal Infomation, Availability .................. 22
FIDONEWS 30-02 Page 1 14 Jan 2013
=================================================================
FOOD FOR THOUGHT
=================================================================
All governments suffer a recurring problem:
Power attracts pathological personalities.
It is not that power corrupts but that it is
magnetic to the corruptible.
Such people have a tendency to become drunk on
violence, a condition to which they are quickly
addicted.
-- Frank Herbert
-----------------------------------------------------------------
FIDONEWS 30-02 Page 2 14 Jan 2013
=================================================================
GENERAL ARTICLES
=================================================================
Some notes on the best place for the host name.
By Michiel van der Vlist 2:280/5555
The best place for IP connect info is the system name field. Why?
1) It is one of the oldest methods of listing IP info, if not THE
oldest. As a result, it is recognised by most if not all of the
IP mailer software that makes use of the nodelist. The INA flag
OTOH came into being much later in the game and so many of the
early IP mailers do not recognise the INA flag and they never will
because it is abandonware.
2) There is no backward compatibility problem. POTS/ISDN mailers
NEVER attempt to extract connect info from the system name field.
In fact they do nothing with the system name field at all.
Nodelist processing software often passes it on to the user for
his information, but the mailer ignores it. Whatever you put there,
it can do no harm to a POTS/ISDN mailer.
3) It is a logical place for a host name. Nomen est omen. The name
says it. A host name is the name by which the system can be addres-
sed in a newtwork. If we wish to address a system on the InterNet
by NAME, what better place to put it then in the systen NAME field?
Some claim there is a potential problem because a system name that is
just that, could be mistaken for a host name or e-mail address. Some
even claim it happens "often".
I say this is a FUD (Fear Uncertainty and Doubt) argument. There is
not a single reported incident where a system name was mistakingly
interpreted as a host name by an IP mailer. It is easy to see why
this should never happen when the specs are followed.
1) The "problem" only applies when the node carries IP flags. For a
POTS/ISDN node is does not matter what is in the system name field.
If it looks like a host name or e-mail address, there is no problem
because a POTS/ISDN mailer will never look there for connect info.
POTS/ISDN mailers looks in the phone number field and nowhere else.
2) It is not all that hard to distinguish a host name, an email
address or a literal IPv4 or IPv6 address from a random string.
At the end of this article I publish the C routines I use to do
that. I wrote them over 7 years ago. I patched them up and made a
shell around it for testing. It felt good to fire up the compiler
and do a bit of programming again. Compile it for your favorite OS
or download the precompiled 16 bit DOS version from my system.
Play around with it...
3) The proper order to look for IP connect info is:
FIDONEWS 30-02 Page 3 14 Jan 2013
A) Parameter field of the flag for the protocol in use.
B) Parameter flag of an INA flag if present.
C) The system name field.
Both the system name field and the INA flag only provide the default
connect information. If the node lists several IP protocols for
connectivity and it does not use the same host name or IP address for
all of them, the odd one out, should have the info in the parameter
field of the flag in question. That overrides the default. So the
parameter field of the protocol flag is the first place to look. If
the connect info is all there, look no further. What is in the system
name field is irrelevant in that case.
When the info is not in the protocol flag but it is in the INA flag
look no further. What is in the system name field is irrelevant in
that case too.
So when it is not in the protocol flag and not in the INA flag, the
system name field is where it MUST be. An IP capable system not ha-
ving IP information in the protocol flag or an INA flag but listing
a system name that only looks like IP info, is simply a listing in
error as it lists IP flags, but no valid IP connect info.
So what about the INA flag? Isn't that a better place for the host
name? I already mentioned that it is a relatively new flag that older
abandonware will not recognise. Other than it is my personal not so
humble opinion that the INA flag is an abomination that should never
have been introduced in the nodelist.
1) It was created for the wrong reasons. The trigger for its concep-
tion was some idiot NC crashing the nodelist production by tag-
ging the same long host name to every IP protocol flag that he
could think of. The version of MAKENL in use at the time crashed
when a line was longer than 157 characters. Of course he could
simply have put the host name in the system name field and it
would gave been processed without problems by MAKENKL, but this
idiot want to make a statement. At the time there was a very vocal
group of sysops that refused to "sacrifice" - as they called it -
the place for the bronze plaquette with the name for their BBS.
And instead of telling these selfish sysops that they can't always
get what they want, the powers that be gave in and adopted the INA
flag. The INA flag is a "technical" solution to what is basically a
social problem. Such a "solution" should evoke reverse peristaltic
movement in any technician worth his keyboard..
2) It does not "fit in" and that makes the life of programmers harder.
When we classify the IP flags, we can see two classes:
A) IP protocol flags, IBN, IFC, IFT, ITN, IVM
These may carry a host name and a port number as parameter.
B) E-mail flags. IEM, ITX, IUC, IMI, ISE
These may carry an e-mail address as parameter.
When writing a parser for a syntax checker, we do not want to hard
code all the flags. So that when a new protocol flag is introduced,
FIDONEWS 30-02 Page 4 14 Jan 2013
we do not have to issue a new version of the programme. We want to
make the list of flags configurable. For that it is convenient if they
can be easily classified. Before the INA flag, we had two classes. A
and B as above. But the INA flag does not fit into one of these
classes. We have to create a whole new class for it:
C) Address carrying flag: INA.
It MUST carry a host name, but not a port number.
So now we have a new class for just ONE flag. And that list of one
flag will never grow, because one "address carrying flag" is all we
ever need. A whole new class for one flag. Argghh!
What makes it even more sad is that the whole circus could have been
avoided by adopting a scheme that has been in use in fidonet for a
very long time: inherit from the predecessor. When listing multiple
node numbers as in via lines, we do not list the full number every
time. When the zone and net number is the same as that of the previous
number, we just list the node number and assume the zone end net
number is the same. Like:
2:280/0 1010 1011 1012 292/1 2 4
We could have done the same for IP protocol flags. When a protocol
flag carries no host name, look at the flag that precedes it and take
it form there:
IBN:example.com,ITN:6023,IFC.
No need for a new class with only one flag .. No need to sacrifice the
BBS name. Well, would have, could have...
The only problem is that it does not work. It does not work because
unlike in the example with the node numbers, the parser may not find
the predecessor. In the example above, it may not know the IBN flag
because it does not support that protocol. Had we agreed on a minimum
protocol for IP nodes that all must support, we would not have this
problem, but we did not and it is unlikely that we ever will. Would
have, could have... Exit the "inherit" method and back to square one.
So the system name field is still the best place for the host name.
And last but not least: what is the worst place for IP connect info?
That is the telephone number field. Why?
1) It creates a serious backward compatibility problem. No matter what
some claim, there are POTS/ISDN mailers out there that can NOT be
configured to never attempt to dial certain numbers. They can
translate numbers to add or change dial prefixes and such and dial
the translated number, but they can not be configured to not dial
at all They are designed on the premise that anything other than
-Unpublished- in field six in the nodelist, is a valid dialable
telephone number. In the general case, there is really no way to
tell what will happen if a classic POTS mailer with a modem a
ttempts to dial a host name. If you are lucky it will do nothing.
FIDONEWS 30-02 Page 5 14 Jan 2013
If not, it may attempt to dial the letters a-d as the "digits" in
the fourth column of the DTMF tone table. Or.. it might attempt to
dial the letters a-z as translated into digits according to the
labelling on the buttons of a push button telephone. No way to
tell, but it may saddle someone with a hefty phone bill. A big
NONO in Fidonet. The telephone number field should contain the
string "-Unpublished-" or a valid dialable telephone number and
nothing else.
2) It creates a problem for dual capability nodes. You can not put a
host name AND a telephone number there.
Just for completeness let me mention the proposed method of listing
the IP info in the location field after the location separated by a
'#' character. That method was abandoned after a brief experimental
stage. Good riddance.
So here is the code I mentioned:
======= iptest.c =======
/* Test my IP detection routines. ╕ 2008-2013 Michiel van der Vlist.
This code is released to the public under the GNU General
Public License. Feel free to use whatever is of use to you. */
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <ctype.h>
#define boolean char
#define TRUE 1==1
#define FALSE !TRUE
#define NONE 0
#define PORTNR 1
#define IPQUAD 2
#define IPV6 3
#define HOSTNAME 4
#define EMAIL 5
int isip(char *s);
boolean isportnumber(char *s);
boolean isipquad(char *s);
boolean isipv6(char *s);
boolean ishostname(char *s);
boolean isemailaddress(char *s);
char sep=':';
int main(int argc, char *argv[])
{
int n;
char s[128];
if (argc>1) sep=argv[1][0];
FIDONEWS 30-02 Page 6 14 Jan 2013
printf("Test the IP detecting stuff.\n");
printf("By Michiel van der Vlist 2:280/55555\n");
printf("# or ^C to abort.\n");
while (TRUE)
{
printf("\nEnter a string: ");
scanf("%s",s);
if (strcmp(s,"#")==0) exit(0);
n=isip(s);
switch (n)
{
case NONE: printf("%s is just a string.\n",s); break;
case PORTNR: printf("%s is a port number.\n",s); break;
case IPQUAD: printf("%s is an ip quad.\n",s); break;
case IPV6: printf("%s is an IPV6 address.\n",s); break;
case HOSTNAME: printf("%s is a host name.\n",s); break;
case EMAIL: printf("%s is an e-mail address.\n",s); break;
default: printf("%s does not parse.\n",s);
}
}
}
/* See if a string qualifies as a parameter for an IP flag */
int isip(char *s)
{
if (isportnumber(s)) return(PORTNR);
if (isipquad(s)) return(IPQUAD);
if (isipv6(s)) return(IPV6);
if (ishostname(s)) return(HOSTNAME);
if (isemailaddress(s)) return(EMAIL);
return(NONE);
}
/* See if a string qualifies as a port number
an up to five digit decimal number qualifies */
boolean isportnumber(char *s)
{
int i=0;
char c;
while ((c=s[i])!=0 && c!=':' && c!=',')
{
if (!isdigit(c) || i>4) return(FALSE);
i++;
}
return(TRUE);
}
/* See if a string qualifies as an ip quad */
/* four nummeric values in the range 0-255,0-255,0-255,0-255
FIDONEWS 30-02 Page 7 14 Jan 2013
separated by dots.
0.0.0.0 is invalid */
boolean isipquad(char *s)
{
int n1,n2,n3,n4,dots;
long unsigned int ipadr;
dots=sscanf(s,"%d.%d.%d.%d",&n1,&n2,&n3,&n4);
if (dots<4) return (FALSE); /* too few fields */
if (n1<0 || n2<0 || n3<0 || n4<0) return (FALSE);
if (n1>255 || n2>255 || n3>255 || n4>255) return (FALSE);
ipadr=(((unsigned long)n1)<<24)+(((unsigned long)n2)<<16)+
(((unsigned long)n3)<<8)+(unsigned long)n4;
if (ipadr==0) return(FALSE);
return(TRUE);
}
/* See if a string qualifies as an ipv6 address */
/* The separator character (colon in the IP world) is defined in the
global variable sep, default also a colon in this test program.
Eight hexadecimal values in the range 0-FFFF separated by a SEP
char. The string may be encased in square brackets and then the
separation character is always a colon. (':')
One or more successive zero values may once be represented by
two successive separators. F.e. 1234::6789:abcd expands to
1234:0:0:0:0:0:6789:abcd.
All zeros is invalid. */
boolean isipv6(char *s)
{
int i=0,j=0,n1,n2,n3,n4,n5,n6,n7,n8,seps=0,nrseps=0,doubleseppos=0;
char c,sp,t[40],tt[40];
char *b;
boolean encased=FALSE;
/* first see if it is encased */
if (s[i]=='[')
{
if (((b=strchr(s,']'))==NULL)) return(FALSE);
else
{
/* there must be one and only one closing bracket */
if(strchr(&b[1],']')!=NULL) return(FALSE);
encased=TRUE; i++; sp=':';
}
}
FIDONEWS 30-02 Page 8 14 Jan 2013
else
{
if (strchr(s,']')!=NULL) return(FALSE);
sp=sep;
}
/* first substitute the separator character by a comma, count them and
note the position of two successive separators on the fly */
while (s[i] && i<sizeof(t)-2 && (!encased || s[i]!=']'))
{
c=s[i];
if (c==sp)
{
c=',';
nrseps++;
if (s[i+1]==sp)
{
if (!doubleseppos) doubleseppos=j; else return FALSE;
}
}
i++;
t[j++]=c;
}
t[j]=0;
/* printf("%s %d %d\n",t,doubleseppos,nrseps); */
/* Now expand the string if there is a double separator present */
if (doubleseppos)
{
strcpy(tt,&t[doubleseppos+1]);
t[doubleseppos]=0;
for (i=0;i<8-nrseps;i++) strcat(t,",0");
strcat(t,tt);
}
seps=sscanf(t,"%x,%x,%x,%x,%x,%x,%x,%x",&n1,&n2,&n3,&n4,
&n5,&n6,&n7,&n8);
if (seps<8) return (FALSE); /* too few fields */
if (doubleseppos) printf("Expands as %s\n",t);
if ((n1+n2+n3+n4+n5+n6+n7+n8)==0) return (FALSE);
return (TRUE);
}
/* see if a string qualifies as a host name */
/* It must contain one or more dots. The dots may not be the first,
the last or the one but last character (no single letter TLDs).
Two dots may not immidiately follow each other.
It must consist of the characters a..z, A..Z,, 0..9, '.', '-'.
The first character must be a letter or a digit. It must contain
at least one letter */
boolean ishostname(char *s)
FIDONEWS 30-02 Page 9 14 Jan 2013
{
int i=1;
char c;
boolean dot=FALSE, letter=FALSE;
if (!isalnum(s[0])) return(FALSE);
while ((c=s[i])!=0 && c!=',' && c!=':')
{
if (isalpha(c)) letter=TRUE;
if (c=='.')
{
dot=TRUE;
if (s[i-1]=='.') return(FALSE);
}
if (!(isalnum(c) || c=='-' || c=='.')) return(FALSE);
i++;
}
if (s[0]=='.' || s[i-1]=='.' || s[i-2]=='.') return(FALSE);
return(dot && letter);
}
/* see if a string qualifies as an email address */
/* It must contain exactly one ampersand character that may not be
the first or the last character. The part after the ampersand must
contain at least one dot. A dot may not be the first, the last or
last but one character. (No single character TLDs) Two dots
may not immidiately follow each other. The ampersand may not be
immidiately followed or preceded by a dot. The string must consist
of the characters a..z, A..Z, 0..9, '.', '-', '_', '@'.
The first character must be a letter. */
boolean isemailaddress(char *s)
{
int i=1, ampersand=0;
char c;
boolean dot=FALSE;
if (!isalpha(s[0])) return(FALSE);
while ((c=s[i])!=0)
{
if (c=='@')
{
ampersand++;
if (s[i-1]=='.') return(FALSE);
}
if (c=='.' && i>0)
{
if (ampersand) dot=TRUE;
if (s[i-1]=='.' || s[i-1]=='@') return(FALSE);
}
if (!(isalnum(c) || c=='-' || c=='.' || c=='_' || c=='@'))
return(FALSE);
i++;
FIDONEWS 30-02 Page 10 14 Jan 2013
}
if (s[0]=='.' || s[i-1]=='.' || s[i-2]=='.') return(FALSE);
if (s[0]=='@' || s[i-1]=='@') return(FALSE);
return (dot && (ampersand==1));
}
====== end iptest.c =====
╕ Michiel van der Vlist, all rights reserved.
Permission to publish in the FIDONEWS file echo, the FIDONEWS dis-
cussion echo and the FNEWS_PUBLISH echo as originating from 2:2/2.
-----------------------------------------------------------------
FIDONEWS 30-02 Page 11 14 Jan 2013
=================================================================
WARD'S WONDERING WAYS
=================================================================
WWW ... Ward's Wondering Ways
By Ward Dossche - 2:292/854
Reader's Digest has been known for decades, or more, for the
condenced version of severtal literary works which they published.
In September 1982 their version of the Bible hit the bookstands,
it had been cut down to 40% of its original size.
I wonder what would happen if they did that to the Quran, or
The Book of Mormon or Lafayette Ronald Hubbard's "Dianetics".
Nevertheless, one thing is certain: they won't do it to the Harry
Potter books.
Why not you may ask?
Simply because of the GIGO-principle ... "Garbage In, Garbage out"
-----------------------------------------------------------------
FIDONEWS 30-02 Page 12 14 Jan 2013
=================================================================
JAMNNTPD SERVERS LIST
=================================================================
The Johan Billing JamNNTPd project
This is a list of known JamNNTPd servers working. They are essentially
the modern version of Bulletin Board Systems.
You connect to them using the email client of your choice and you
don't need any other software installed on your computer -- regardless
of operating system -- but that favourite mail client of yours.
Even smart phones can handle this, giving you the opportunity to get
your daily doses of fidonet on the bus, tram or train on the way to
your job, school or whatever.
Updated 2012-03-11
URL news://felten.yi.org
Join http://felten.yi.org/join.html
NETMAIL Yes, 2:203/2
URL news://the-estar.com:1119
Join http://www.easternstar.info
NETMAIL Yes, 1:123/789
URL news://quinnspost.dyndns.org:60119
Join mailto:eskimo261@bigfoot.com
NETMAIL No
URL news://nntp.rbb.bbs.fi
Join Info in group +GETACCESS+
NETMAIL Yes, 2:221/361
URL news://news.wpusa.dynip.com
Join Info in group +GETACCESS+
NETMAIL Yes, 1:3634/12
-----------------------------------------------------------------
FIDONEWS 30-02 Page 13 14 Jan 2013
=================================================================
FIDONEWS'S FIDONET SOFTWARE LISTING
=================================================================
-=:{ FidoNet Software Reference }:=-
Type: M=Mailer T=Tosser B=BBS D=Door C=Comm/Terminal
P=Points E=Editor I=Internet U=Utility ?=Info
.- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.
|Software: Author |Type |URL, Contact, Ver, Notes Help Node|
`- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -'
Argus |MI |http://www.ritlabs.com/argus/ 2:469/84
| | argus@ritlabs.com Tel: 373-2-246889
| | v3.210 on Mar 20th 2001
BinkleyTerm XE |M |http://btxe.sourceforge.net 1:1/102
| | v2.60XE/Gamma-6 on Nov 11th 1998
BinkD |MI |http://binkd.grumbler.org/ 2:463/69
| | v0.9.10 on Oct 2nd 2008
D'Bridge |MTCPE|http://www.net229.org/dbridge.htm 1:1/130
Nick Andre |I | v3.8 on July 10 2012
FIDO-Deluxe IP |MPUI |http://www.fido-deluxe.de.vu 2:2432/280
Michael Haase | | m.haase@gmx.net
| | v2.4 on Sep 26th 2003
FrontDoor, FD/APX: |MTPC |http://www.defsol.se 2:201/330
Definite Solutions | | sales@defsol.se 1:1/101
| | v2.26SW & v2.33ml FD, v1.15 APX
Husky Project |MTPUI|http://sf.net/projects/husky/
| | v1.4 RC5 on Apr 24th 2006
Radius |MI |http://radius.pp.ru 2:5012/38
(based on Argus) | | fido5012@zaural.net Tel: 7-3522-469463
| | Last Release: v4.010 on Jan 3nd 2005
Taurus |MI |http://taurus.rinet.ru (Russian) 2:461/70
| |http://www.fidotel.com/taurus (English)
(based on Radius) | | E-mail: taurus@rinet.ru
| | v5.000 alpha on Oct 11th 2004
Tmail |MI |http://www.tmail.spb.ru v2608
| | Website is in Russian only
WildCat! Interactive |MTBEI|http://www.santronics.com
Net Server, Platinum| | sales@santronics.com
Xpress: Santronics | | Tel: (305) 248-3204
Software, Inc. | | AUP 451.1 on April 26th 2004
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
Fidogate |TUI |http://www.fidogate.org
FIDONEWS 30-02 Page 14 14 Jan 2013
| | Martin_Junius@m-j-s.net v4.4.10
FMail |T |http://sourceforge.net/projects/fmail/
| | v1.60.GPL
JetMail: JetSys |TU |http://www.jetsys.de js@jetsys.de
(ATARI ST only) | | v1.01 on Jan 1st 2000
Squish |T |http://maximus.sourceforge.net/
| | Lanuis site redirects to above
| | Squish is part of Maximus.
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
BBBS |BI |http://www.bbbs.net b@bbbs.net
| | v4.00MP on Oct 25th 1999 2:22/222
ELEBBS: The Elevator |B |http://www.elebbs.com
Software Production | | elebbs@elebbs.com
| | v0.10.RC1 on Jun 9th 2002
Ezycom BBS |BT |http://www.ezycom-bbs.com
| | ezycom@amnet.net.au or
| | ezycom_hq@ezycom-bbs.com 3:690/682
| | v2.15g2 on 16 Nov 2009
Hermes II Project |B |http://www.hermesii.org
| | info@HermesII.org v3.5.9 Beta Final
Maximus BBS |B |http://maximus.sourceforge.net/
| | v3.03
| |Archives back online at:
| |http://maximus.outpostbbs.net/
MBSE BBS: |BI |http://mbse.sourceforge.net 2:280/2802
Michiel Broek | | mbroek@users.sourceforge.net
| | v0.60.0 on June 5th 2004
Mystic BBS |B |http://www.mysticbbs.com
| | v1.07.3 on May 13th 2001
Nexus BBS |B |http://www.nexusbbs.net
| | groberts@nexusbbs.net
| | v0.99.41-Beta on Oct 16th 2002
| | [Note: No Longer under active
| | development.]
Proboard BBS |B |http://www.proboard.be
| | v2.17 on Jun 9th 2002
RemoteAccess BBS: |B |http://www.rapro.com 1:1/120
Bruce Morse | | bfmorse@rapro.com
| | v2.62.2SW
Spitfire BBS: Buffalo|B |http://www.angelfire.com/ia/buffalo/
Creek Software | | MDWoltz@aol.com 1:1/150
FIDONEWS 30-02 Page 15 14 Jan 2013
| | v3.6 on Aug 20th 1999
Synchronet BBS |BT |http://www.synchro.net
| | sysop(at)vert(dot)synchro(dot)net
| | v3.10L Beta
Telegard BBS |B |http://www.telegard.net
| | support@telegard.net
| | v3.09g2 SP4
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
Atlantis Software |D |http://www.jimmyrose.com/atlantis/
| | Last Update: August 2004
Cheepware |DU |http://outpostbbs.net
Sean Dennis | | sean@outpostbbs.net 1:18/200
DDS (Doorware |D |http://www.doorgames.org 1:2404/201
Distribution System)| | ruth@doorgames.org
Ruth Argust | |
DoorMUD |D |http://doormud.com
| | v0.98 Jun 1st 2002
| | Website is down after
| | past the splash page.
Jibben Software |D |http://www.jibbensoftware.com
| | scott@jibben.com
| | 1995-99 Release dates
John Dailey Software |D |http://www.johndaileysoftware.com
| | support@johndaileysoftware.com
Shining Star |D |http://www.shiningstar.net/bbsdoors/
| | nannette@shiningstar.net
Sunrise Doors: |D |http://www.sunrisedoors.com
Al Lawrence | | al@sunrisedoors.com
| | Tel: (404) 256-9518
The Brainex System |D |http://www.brainex.com/brainex_system/
| | stanley@brainex.com 1994-99 Releases
Trade Wars |D |http://www.eisonline.com/tradewars/
| | jpritch@eisonline.com
| | v3.09 (DOS-32) in 2002
Vagabond Software: |D |http://www.vbsoft.org 1:124/7013
Bryan Turner | | vagabond@vbsoft.org
| | last update: Jul 17th 2002
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
APoint |PI |http://www.apoint-mail.de 2:2426/1210.13
| |http://www.apoint-mail.de/indexe.htm
| | (English Version)
FIDONEWS 30-02 Page 16 14 Jan 2013
| | dirk.pokorny@apoint-mail.de
| | v1.25
CrossPoint (XP) |P |http://www.crosspoint.de (German Only)
| | pm@crosspoint.de v3.12d Dec 22nd 1999
FreeXP |P |http://www.freexp.de 2:2433/460
| | support@freexp.de
| | v3.40 RC3 Aug 31st 2003 (Snapshot)
OpenXP/32 |PI |http://www.openxp.com 2:248/2004
| | (Site is in German Only)
| | mk@openxp.de v3.8.15 Beta Feb 10th 2004
| | Download Page comes back 404 not found.
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
GoldEd+ |E |http://golded-plus.sourceforge.net/
| | 2:5080/102
| | stas_degteff@users.sourceforge.net
| | v1.1.5 Snapshot on Feb 28th 2003
SqEd32 |E |http://www.sqed.de
| | v1.15 on Dec 15th 1999
TimEd |E |http://blizzard.dnsalias.org/fidonet
| | mail@ozzmosis.com /timed
| | v1.11.a5 in March 2003 3:633/267
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
FidoIP |MTPEIU|http://sourceforge.net/projects/fidoip
| | Maxim Sokolsky 2:5020/828.777
| | v.0.5_1 on Jan 11 2010
GiGo |UI |http://www.gigo.com
| | v0109 on Jan 9th 1997
Ifmail |UI |http://ifmail.sourceforge.net
| | crosser@average.org 2:5020/230
| | Ifmail is a FTN <-> E-Mail/News Gateway
| | Program.
Internet Rex: |UI |http://members.shaw.ca/InternetRex/
Charles Cruden | | telnet://xanadubbs.ca 1:342/806
(Khan Software) | | v2.29 on Oct 21st 2001
MakeNL |U | http://hub2000.darktech.org/makenl
| | fidonet.hub2000 [at] gmail [dot] com
| | Fido: 1:229/2000
| | FidoNet Nodelist Processor
Meltdown-BBS |UI |http://meltdown-bbs.sourceforge.net/
| | meltdown-bbs.project.petkan
| | @spamgourmet.com
| | Fido: 2:350/5
FIDONEWS 30-02 Page 17 14 Jan 2013
| | Meltdown-BBS is an FTN <->
| | Web/PHP/MySQL BBS forum system.
RNtrack |U |http://sourceforge.net/projects/ftrack-as
| |2:5080/102
| |stas_degteff@users.sourceforge.net
| | v1.1.4 Snapshot on Oct 09 2009
TransNet |UI |http://www.ressl.com.ar/transnet/
| | transnet@ressl.com.ar
| | v2.11 on Jul 18th 1998
TransX: Multiboard |UI |http://www.start.ca/software/multiboard
Communications, Inc.| | Unsure about support now but Free Keys
| | are now available. Donations accepted.
| | v3.5 (Note: KeyGen is a Windows Program)
Turquoise SuperStat |U |http://www.softwolves.pp.se/sw/
| | software/turquoise
| | peter@softwolves.pp.se
| | Version: 3.0 on 2008-01-21
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
National BBS List |? | http://www.usbbs.org
Hispanic FIDO/BBS's |? | http://www.conecta2.org/pucela_bbs/
(in Spanish only) | | (Extensive software & BBS Listings)
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
File Archives:
http://archives.thebbs.org http://www.filegate.net
http://sysopscorner.thebbs.org http://www.juge.com
http://www.dmine.com/bbscorner/ http://garbo.uwasa.fi
http://www.simtel.net http://wuarchive.wustl.edu
http://www.bbsfiles.com http://hobbes.nmsu.edu
Note: most also provide FTP access
(use ftp:// instead of http:// above)
*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*=.=*=-=*
Please send corrections & additions to: Fidonews Editor
Emeritus: Robert Couture, Ben Ritchey, Todd Cochrane,
Frank Vest, Peter Popovich
-----------------------------------------------------------------
FIDONEWS 30-02 Page 18 14 Jan 2013
=================================================================
SPECIAL INTEREST
=================================================================
Nodelist Stats
Input nodelist nodelist.011
size 329.6kb
date 2013-01-11
The nodelist has 2301 nodes in it
and a total of 3361 non-comment entries
including 4 zones
35 regions
236 hosts
195 hubs
admin overhead 470 ( 20.43 %)
and 308 private nodes
121 nodes down
161 nodes on hold
off line overhead 590 ( 25.64 %)
Speed summary:
>9600 = 169 ( 7.34 %)
9600 = 1482 ( 64.41 %)
(HST = 21 or 1.42 %)
(CSP = 0 or 0.00 %)
(PEP = 1 or 0.07 %)
(MAX = 0 or 0.00 %)
(HAY = 1 or 0.07 %)
(V32 = 706 or 47.64 %)
(V32B = 48 or 3.24 %)
(V34 = 976 or 65.86 %)
(V42 = 827 or 55.80 %)
(V42B = 51 or 3.44 %)
2400 = 11 ( 0.48 %)
1200 = 2 ( 0.09 %)
300 = 637 ( 27.68 %)
ISDN = 158 ( 6.87 %)
----------------------------------------------------------
File Req Flag Applicable software Number of systems
----------------------------------------------------------
XA Frontdoor <1.99b 662
Frontdoor 2.02+
Dutchie 2.90c
Binkleyterm >2.1
D'Bridge <1.3
TIMS
Xenia
--------------------------------------
FIDONEWS 30-02 Page 19 14 Jan 2013
XB Binkleyterm 2.0 0
Dutchie 2.90b
--------------------------------------
XC Opus 1.1 1
--------------------------------------
XP Seadog 0
--------------------------------------
XR Opus 1.03 16
--------------------------------------
XW Fido >12M 66
Tabby
KittenMail
--------------------------------------
XX D'Bridge 1.30 718
Frontdoor 1.99b
Intermail 2.01
T-Mail
--------------------------------------
None QMM 838
--------------------------------------
CrashMail capable = 1157 ( 50.28 %)
MailOnly nodes = 1137 ( 49.41 %)
Listed-only nodes = 183 ( 7.95 %)
Other = -176 ( -7.65 %)
[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/208]
-----------------------------------------------------------------
FIDONEWS 30-02 Page 20 14 Jan 2013
=================================================================
FIDONEWS INFORMATION
=================================================================
How to Submit an Article
If you wish to submit an article for inclusion in the Fidonews, here
are some guidelines, if you send it as an attached file; the preferred
method if you want reasonable control over how the published article
will appear in the Fidonews:
a) Plain ASCII text. If you could type it on your keyboard, it's
probably quite OK. No line may be longer than 70 characters.
b) Put a title to the article. Put the title in two times. The first
time, on the first line, with an * before it. The second time, on
the second line, without the * and centered. This will help in the
format since the title with the * is removed and used in the index,
the second line will become the headline. On the third line, put
your name and FidoNet address, present or former. If former, you
may want to add some other address where you can be reached for
personal comments.
c) Deadline for article submission is Sunday, 22:00 UTC.
Help the Editor by following the above guides. Below are some subjects
and the file extension for the article as set in the configuration
file for the making of the Fidonews. Please help by putting the file
extension of the correct subject on the file name if known.
Ideas for Subject areas:
Subject File | Subject File
----------------------------------|----------------------------------
From the *C's *.css | Rebuttals to articles *.reb
Fidonet Regional News *.reg | Fidonet Net News *.net
Retractions *.rtx | General Fidonet Articles *.art
Guest Editorial *.gue | Fidonet Current Events *.cur
Fidonet Interviews *.inv | Fidonet Software Reviews *.rev
Fidonet Web Page Reviews *.web | Fidonet Notices *.not
Getting Fidonet Technical *.ftc | Question Of The Week *.que
Humor in a Fido Vein *.hfv | Comix in ASCII *.cmx
Fidonet's Int. Kitchen *.rec | Poet's Corner *.poe
Clean Humor & Jokes *.jok | Other Stuff *.oth
Fidonet Classified Ads *.ads | Corrections *.cor
Best of Fidonet *.bof | Letters to the Editor *.let
If you don't know or are not sure, send the article anyway. Put a .TXT
on it and I'll try to figure out where it should be in the Fidonews.
If you follow these simple guidelines, there should be little problem
in getting your article published. If your submission is too far out
of specs for the Fidonews, it will be returned to you and/or a message
sent informing you of the problem. This DOES NOT mean that your
article is not accepted. It means that there is something in it that I
can not fix and I need your help on it.
FIDONEWS 30-02 Page 21 14 Jan 2013
Send articles via e-mail or netmail, file attach or message to:
Björn Felten
Fidonet 2:2/2 or 2:203/0
E-Mail bfelten @ telia dot com
Skype file bfelten
IMPORTANT! If you send the article via e-mail, make sure you put the
word "fidonews" somewhere in the subject line! That way it
will always pass the spam filter, ending up in the proper
folder.
Please include a message, telling me that you have sent an article.
That way I will know to look for it.
-----------------------------------------------------------------
FIDONEWS 30-02 Page 22 14 Jan 2013
Credits, Legal Infomation, Availability
+ -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
| |
| Editor: Björn Felten, 2:2/2 |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
+ -- -- -- -- -- -- -- - EDITORS EMERITI - -- -- -- -- -- -- -- +
| |
| Tom Jennings, Thom Henderson, Dale Lovell, Vince |
| Perriello, Tim Pozar, Sylvia Maxwell, Donald Tees, |
| Christopher Baker, Zorch Frezberg, Henk Wolsink, |
| Doug Meyers, Warren D. Bonner, Frank L. Vest |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
Fidonews is published weekly by and for the members of Fidonet.
There is no copyright attached to Fidonews, though authors
retain rights to their contributed articles. Opinions expressed
by the authors are strictly their own. Noncommercial duplication
and distribution within Fidonet is encouraged. Authors are
encouraged to send their articles in ASCII text to the Editor
at one of the addresses above.
The weekly edition of Fidonews is distributed through the file
area FIDONEWS, and is published as echomail in the echo FIDONEWS.
The different articles are distributed in the file area SNOOZE.
A service to various projects for making Fidonews available on
the web with a more pleasing lay-out.
These sources are normally available through your Network
Coordinator. The current and past issues are also available from
the following sources:
+ -- -- -- -- -- -- - FIDONEWS AVAILABILITY - -- -- -- -- -- -- +
| |
| File request from 2:2/2 or 2:203/0: |
| current issue FIDONEWS |
| back issue, volume v, issue ii FNEWSvii.ZIP |
| articles, vol.no nn, issue ii INPUnnii.ZIP |
| |
| On the web: |
| http://felten.yi.org/fidonews |
| http://fidonews.eu |
| |
| The Snooze *and* the FIDONEWS echo in your newsreader: |
| news://felten.yi.org/FIDONEWS |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
-----------------------------------------------------------------
Download original FidoNews · Volume 30 (2013) · ← Previous · Next →