FidoNews · Vol 31, No 38 · 22 Sep 2014
The F I D O N E W S Volume 31, Number 38 22 Sep 2014
+--------------------------+-----------------------------------------+
| |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: |
| _ @/_ \ _ | b @ felten dot se |
| | | \ \\ | |
| | (*) | \ ))| |
| |__U__| / \// | Editor: Björn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER |
+--------------------------+-----------------------------------------+
Table of Contents
1. FTSC INFORMATION ......................................... 1
Publication: FTS-1030 ................................. 1
2. LIST OF FIDONET IPV6 NODES ............................... 6
List of IPv6 nodes ....................................... 6
3. JAMNNTPD SERVERS LIST .................................... 7
The Johan Billing JamNNTPd project ....................... 7
4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 8
FidoNet Software References .............................. 8
5. SPECIAL INTEREST ......................................... 13
Nodelist Stats ........................................... 13
6. FIDONEWS INFORMATION ..................................... 15
How to Submit an Article ................................. 15
Credits, Legal Infomation, Availability .................. 17
FIDONEWS 31-38 Page 1 22 Sep 2014
=================================================================
FTSC INFORMATION
=================================================================
Publication: FTS-1030
**********************************************************************
FTSC FIDONET TECHNICAL STANDARDS COMMITTEE
**********************************************************************
Publication: FTS-1030
Revision: 1
Title: Binkp optional protocol extension CRC Checksum.
Authors: Tobias Ernst (publisher of this protocol),
Michiel Broek (documentation for FTSC).
FTSC members and administrator.
Date: 2014-09-21
----------------------------------------------------------------------
Contents
--------
1. Definitions
2. Binkp CRC Checksum Mode
2.1 Introduction
2.2 Protocol specification
2.3 Further thoughts
2.4 CRC-32 Algorithm
3. Compatibility issues
A. References
B. History
----------------------------------------------------------------------
Status of this document
-----------------------
This document is a FidoNet Technical Standard (FTS).
This document specifies an optional FidoNet standard for the FidoNet
community.
This document is released to the public domain, and may be used,
copied or modified for any purpose whatever.
This document supersedes and replaces FSP-1020.
FSP-1020 is preserved in the FTSC reference library as FRL-1022.
The CRC algorithm described in this document can be used for file
forwarding as explained in FSC-0028 and might be easier to
understand. Note that FSC-0060 also describes CRC algorithms. Do
not use it, the algorithm documented in FSC-0060 is in error.
1. Definitions
--------------
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
FIDONEWS 31-38 Page 2 22 Sep 2014
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [FTA-1006].
2. Binkp CRC Checksum Mode
--------------------------
2.1 Introduction
----------------
Binkp originally was designed to work on top of a reliable
transmission layer, i.E. a transmission layer that has its own
checksums, like TCP. Therefore, the Binkp specification does not
provide a way for controlling correct data transfer, because
it is assumed that the underlying TCP transport layer does the
necessary data integrity checks.
However, I have seen TCP connections trashing data at random, and
actually have suffered from mail loss because a file received by
binkd was not identical with the file that the sender has
transmitted.
Therefore, this document specifies an extension to the Binkp
protocol which allows data integrity checks by means of CRC32
checksums. It is intended as an *optional* feature in Binkp for
those nodes that live in places with an unreliable TCP routing
structure (like I seem to do), and it is fully backwards
compatible.
It is highly recommended to use this extension when receiving
files using the optional NR mode (FTS-1028). It will ensure
that any file received in two or more parts matches the file
on the sending system before it is acknowledged, and deleted
by the sending system.
2.2 Protocol specification
--------------------------
During session handshake, a mailer that knows the CRC protocol
extension MAY send an "M_NUL OPT CRC" message. This indicates
that the mailer is able to process the CRC-extended "M_FILE"
messages described below, nothing more.
The other end which receives the OPT CRC message will switch to
CRC-secure mode (probably only if CRC-secure mode has been
allowed by the sysop for the particular other end). Note that
even if this end previously has sent a M_NUL OPT CRC on its own,
it is not forced to switch to CRC mode, it is just an option.
In the following, the "sending end" is the Binkp mailer which is
transmitting a file, and the "receiving end" is the mailer which
is receiving it. Of course, in a Binkp session, both sides can
become both sending and the receiving ends.
When the sending end is in CRC-secure mode, it will send an
FIDONEWS 31-38 Page 3 22 Sep 2014
extended M_FILE message with an additional fifth argument,
specifying a CCITT CRC32 checksum for the file that is following.
This means that the mailer has to calculate the checksum before
transmitting the file.
The checksum is pre-conditioned and postconditioned. This means
that the initial CRC-value is 0xFFFFFFFF (preconditioning), and
after the final value has been computed, all bits must be in-
verted (postconditioning).
The CRC polynomial to be used is:
X^32+X^26+X^22+X^16+X^12+X^11+X^10+X^8+X^7+X^5+X^4+X^2+X^1+X^0.
The format of the fifth M_FILE argument is a sequence of up to
eight hexadecimal digits in ASCII. The letters a-f may be converted
to lower case. Leading zeros may be omitted, trailing digits must
not be omitted.
The receiving end, if it has sent an "M_NUL OPT CRC", MUST be
able to process M_FILE messages with either four or five
arguments. If it receives a M_FILE message with five arguments,
it will treat the fifth argument as a checksum and, after
receiving the file, will compare this checksum with the checksum
it has computed from the data that has been received.
If the checksums disagree, the receiving end has two options. It
can either send a M_SKIP for this file. This will cause a
non-destructive reject of the file, so that the session goes on,
but the remote site will mark the file as not sent successfully
and retransmit it in the next session. Or it can send a M_ERR,
indicating a fatal failure, which will terminate the session,
and also cause a non-destructive reject of this and all following
files. It is suggested that on the first CRC failure, a M_SKIP
is sent, but if the next file also has an error, indicating that
the session is completely faulty, a M_ERR could be transmitted
instead.
2.3 Further thoughts
--------------------
There are some disadvantages of this way of implementing CRC:
1. The CRC checksum must be computed before the file
transmission STARTS, instead of during the transmission.
2. The protocol will fail if errors don't occur spontaneous, but
regularly with an error rate greater than 1 error per file.
In this case, transmission will be impossible because all
files will always be rejected.
Why then implement it this way? It is the easiest way to
implement CRC fully backwards compatible, and it is the way that
requires the least amount of changes in the code of existing
binkp mailers. Even given the mentioned disadvantages, the
FIDONEWS 31-38 Page 4 22 Sep 2014
extension is good enough for detecting spontaneous transmission
errors, so that sysops will not loose valuable data, and so that
they can see that there is a problem in the network infrastructure
and fix it. That is, this extension is intended as a safeguard
against rare error conditions on a transport layer that still,
basically, is reliable.
This extension, however, is not suitable for transmission over a
transport layer which is unreliable by definition, as a standard
modem connection. But that was not the goal of binkp from the
beginning.
In the future, it might be worth considering an extension to the
binkp protocol which goes further. For example, one CRC32
checksum could be transmitted at the end of each frame, and a
mechanism for directly resending frames added.
2.4 CRC-32 Algorithm
--------------------
The checksum algorithm that is used is CRC-32 following ITU-T's
specifications. For further information refer to the literature
list given below. The following pseudocode shows how to
calculate such a checksum for a file of N bytes indexed from 0 to
N-1 and stored in BUFFER. The XOR, AND and NOT logical
operations are to be executed bit-wise. In C, for instance, XOR
equals ^, AND equals &, and NOT equals ~.
// CRC, I, J, K are unsigned integers of at least 32 bits.
UNSIGNED LONG CRC, I, J, K
// Preconditioning
CRC = FFFFFFFF
// Loop through all bytes in the file
FOR J = 0 TO N-1
K = (CRC XOR BYTE#J) & 000000FF // (*)
FOR I = 8 DOWNTO 1
IF K AND 1 <> 0
THEN K = (K SHR 1) XOR EDB88320
ELSE
K = K SHR 1
ENDIF
END FOR // (**)
CRC = ((CRC SHR 8) AND 00FFFFFF) XOR K
END FOR
// Postconditioning: Flip all bits
CRC = NOT CRC;
Note that the initial value of K is limited to the range of 0 up
to 255. (see line marked by '(*)'). Therefore it is a good idea
to replace the inner loop with a lookup table routine, i.e.
generate a lookup table with the results of the inner loop for
the start values of 0 up to 255, and then replace the loop marked
FIDONEWS 31-38 Page 5 22 Sep 2014
by '(*)' and '(**)' with something like:
K = LOOKUPTABLE [ (CRC XOR BYTE#J) XOR 000000FF ]
Author: Tobias Ernst
3. Compatibility issues
-----------------------
The CRC option cannot be used together with some other options
which also use extra parameters with the M_FILE messages. This
currently includes the GZip and BZip2 file compression options.
A. References
-------------
[FTS-1026]
Binkp/1.0 Protocol specification.
[FTA-1006]
Key words to indicate requirement levels, Fidonet Technical
Standards Committee administrative. FTA-1006.
[ITU-T V.42]
International Telecommunications Union, Error-correcting
Procedures for DCEs Using Asynchronous-to-Synchronous
Conversion, ITU-T Recommendation V.42, 1994, Rev. 1.
[ISO 3309]
International Organization for Standardization,
"Information Processing Systems--Data Communication
High-Level Data Link Control Procedure--Frame Structure",
ISO 3309, October 1984, 3rd Edition.
B. History
----------
Rev.1, 2014-09-21: First release.
-----------------------------------------------------------------
FIDONEWS 31-38 Page 6 22 Sep 2014
=================================================================
LIST OF FIDONET IPV6 NODES
=================================================================
List of Ipv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 20 September 2014
Node Nr. Sysop Type Provider Remark
1 2:280/464 Wilfred van Velzen Native Xs4All
2 2:280/5003 Kees van Eeten Native Xs4All
3 2:5019/40 Konstantin Kuzov T-6in4 he.net PO4
4 2:240/1661 Markus Reschke Native DTAG
5 2:280/5555 Michiel van der Vlist T-AYIY SixXs
6 1:320/219 Andrew Leary T-AYIY SixXs
7 2:221/6 Tommi Koivula T-6to4
8 2:5053/54 Denis Mikhlevich ? vtt.ru
9 2:5034/16 Alexey Ignatov T-6in4 he.net
10 2:5030/257 Vova Uralsky T-6in4 he.net
11 1:154/10 Nicholas Boël T-6in4 he.net
12 1:154/701 Nicholas Boël T-6in4 he.net
13 2:203/0 Björn Felten T-6in4 SixXs IO
14 2:280/5006 Kees van Eeten Native Xs4All INO4
15 3:712/848 Scott Little T-6to4 IO
16 2:5020/545 Alexey Vissarionov Native ?
Tunnel type:
T-6in4 Static 6in4
T-AYIY Dynamic AYIYA
T-6to4 6to4
Remarks:
IO Incoming only (Node can not make outgoing IPv6 calls)
INO4 No IPv4 (Node can not accept incoming IPv4 calls)
PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
but is configured to try IPv4 first)
-----------------------------------------------------------------
FIDONEWS 31-38 Page 7 22 Sep 2014
=================================================================
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.nodelist.net:60119
Join mailto:eskimo261@bigfoot.com
Join Info in group +GETACCESS+
NETMAIL Yes, 3:640/384
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 31-38 Page 8 22 Sep 2014
=================================================================
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.99 on Feb 19 2014
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
Mystic BBS |MTBCE|http://www.mysticbbs.com
|I | v1.10 A31 on Apr 13th 2013
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
FIDONEWS 31-38 Page 9 22 Sep 2014
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
Fidogate |TUI |http://www.fidogate.org
| | Martin_Junius@m-j-s.net v4.4.10
FMail |T |http://sourceforge.net/projects/fmail/
| | 1.66.0.33.gpl (2013-10-17)
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
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
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
| | v3.6 on Aug 20th 1999
Synchronet BBS |BT |http://www.synchro.net
| | sysop(at)vert(dot)synchro(dot)net
| | v3.10L Beta
FIDONEWS 31-38 Page 10 22 Sep 2014
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)
| | dirk.pokorny@apoint-mail.de
| | v1.25
CrossPoint (XP) |P |http://www.crosspoint.de (German Only)
| | pm@crosspoint.de v3.12d Dec 22nd 1999
FIDONEWS 31-38 Page 11 22 Sep 2014
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
| | 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
FIDONEWS 31-38 Page 12 22 Sep 2014
| | 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 31-38 Page 13 22 Sep 2014
=================================================================
SPECIAL INTEREST
=================================================================
Nodelist Stats
Input nodelist nodelist.262
size 270.2kb
date 2014-09-19
The nodelist has 1805 nodes in it
and a total of 2602 non-comment entries
including 4 zones
33 regions
204 hosts
168 hubs
admin overhead 409 ( 22.66 %)
and 194 private nodes
91 nodes down
103 nodes on hold
off line overhead 388 ( 21.50 %)
Speed summary:
>9600 = 142 ( 7.87 %)
9600 = 939 ( 52.02 %)
(HST = 14 or 1.49 %)
(CSP = 0 or 0.00 %)
(PEP = 1 or 0.11 %)
(MAX = 0 or 0.00 %)
(HAY = 1 or 0.11 %)
(V32 = 475 or 50.59 %)
(V32B = 43 or 4.58 %)
(V34 = 642 or 68.37 %)
(V42 = 529 or 56.34 %)
(V42B = 45 or 4.79 %)
2400 = 5 ( 0.28 %)
1200 = 2 ( 0.11 %)
300 = 717 ( 39.72 %)
ISDN = 112 ( 6.20 %)
----------------------------------------------------------
File Req Flag Applicable software Number of systems
----------------------------------------------------------
XA Frontdoor <1.99b 454
Frontdoor 2.02+
Dutchie 2.90c
Binkleyterm >2.1
D'Bridge <1.3
TIMS
Xenia
--------------------------------------
FIDONEWS 31-38 Page 14 22 Sep 2014
XB Binkleyterm 2.0 0
Dutchie 2.90b
--------------------------------------
XC Opus 1.1 0
--------------------------------------
XP Seadog 0
--------------------------------------
XR Opus 1.03 15
--------------------------------------
XW Fido >12M 42
Tabby
KittenMail
--------------------------------------
XX D'Bridge 1.30 543
Frontdoor 1.99b
Intermail 2.01
T-Mail
--------------------------------------
None QMM 751
--------------------------------------
CrashMail capable = 1040 ( 57.62 %)
MailOnly nodes = 854 ( 47.31 %)
Listed-only nodes = 109 ( 6.04 %)
Other = -198 (-10.97 %)
[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/2]
-----------------------------------------------------------------
FIDONEWS 31-38 Page 15 22 Sep 2014
=================================================================
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 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 31-38 Page 16 22 Sep 2014
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 b @ felten dot se
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 31-38 Page 17 22 Sep 2014
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 31 (2014) · ← Previous · Next →