FidoNews · Vol 24, No 5 · 29 Jan 2007
The F I D O N E W S Volume 24, Number 05 29 Jan 2007
+--------------------------+-----------------------------------------+
| |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
Frustrations of a FidoNet programmer ..................... 2
3. ROBERT COUTURE'S FIDONET SOFTWARE LISTING ................ 6
FidoNet Software References .............................. 6
4. SPECIAL INTEREST ......................................... 11
Nodelist Stats ........................................... 11
5. FIDONEWS INFORMATION ..................................... 13
How to Submit an Article ................................. 13
Credits, Legal Infomation, Availability .................. 15
FIDONEWS 24-05 Page 1 29 Jan 2007
=================================================================
FOOD FOR THOUGHT
=================================================================
To speak gratitude is courteous and pleasant, to enact gratitude is
generous and noble, but to live gratitude is to touch Heaven.
-- Johannes A. Gaertner
-----------------------------------------------------------------
FIDONEWS 24-05 Page 2 29 Jan 2007
=================================================================
GENERAL ARTICLES
=================================================================
Frustrations of a FidoNet programmer
By Michiel van der Vlist, 2:280/5555
Most of us who have at some point in their career had job descriptions
that included "writing computer programmes" will be familiar with the
frustrations of having to meet with the demands of customers and
management. What customers and managers usually have in common is that
they can not program themselves out of a wet paper bag even if their
lives depend on it, but who nevertheless have firm perceptions on the
ease by which their demands can be met. "I am not a programmer myself,
but this should be easy to add" is heard too often.
All the more frustrating is that ever so often the customer's wish
would have been relatively easy to meet, had the customer come up with
it in an early stage of the project instead of when it is 99%
finished. Honesty compels me to admit that the opposite also happens:
a customer coming up with a wish that just needs a few key strokes to
fulfil, but him/her believing it is major alteration. (And willing to
pay according to his/her beliefs...)
When writing as a volunteer for a non profit organisation such as
FidoNet, one would hope and maybe even expect to be free of such
frustrations and to just be allowed to program for fun. Unfortunately
this is not true. Not any more I am afraid. Let me give you an example
of something I came across while programming for FidoNet.
When I became R28 pointlist keeper over a decade ago now, I felt the
need for a programme that could not only assemble pointlists from
segments, but that would also check things like flags for correct use
as well. There was MakeNl and there was ERRFLAGS, but the latter would
not work on pointlists and I found it too limited as well. MakeNl was
abanonware at the time and I was not satisfied that either. So I
decided to write my own programme.
Part of this programme was to be the flag checker. Of course the flags
that it recognised should not be hard coded, but be configurable. We
have seen too much problems with hard coding, I did not want to saddle
the users of my programme with the the burden of having to nag for an
update every time a new flag was added to the nodelist. Flags should
be configurable.
Sounds easy. Just make the user enter in the config, a list of flags
he would like to have recognised as valid and if the flag is in the
list, it is ok, and if it is not, generate a warning or an error.
Something like:
FLAGS V22,V32,V32B,V90C,V90S,VFC,V34
But wait, there are userflags and normal flags, so we should have two
classes of flags:
FLAGS XA,XB,XC,XP,XR,XW,XX,CM,MO,MN,LO,V42,V42B,MNP,V22,V32,V32B,
FIDONEWS 24-05 Page 3 29 Jan 2007
V32T,ZYX,Z19,HST,H14,H16,MAX,PEP,CSP,VFC,V34,V110L,V110H,
V120H,V120L,X75,ISDN,X2S,X2C,V90S,V90C
USERFLAGS NC,REC,NEC,ZEC,ENC,RPK,NPK,CDP,SDS,SMH
All pretty straightforward. Oh, well, there are the Tyz flags. We do
not want the user to have to enter all 2256 valid permutations all by
himself, so we define wildcards for the flags. The Tyz flags are
added:
USERFLAGS NC,REC,NEC,ZEC,ENC,RPK,NPK,CDP,SDS,SMH,T$$
But only a-x and A-X are actually allowed as substitutes for the
wildcards. And permutations with the same letter in the second and
third position are also invalid. Ok, no problem, exclude those
combinations:
EXCLUDEFLAGS TY$,Ty$,TZ$,Tz$,T$Y,T$y,T$Z,T$z,T$<
It started to get a little complicated by now, but still pretty
straightforward. There was one thing still missing though. Flags can
have parameters. Up until the coming of Fido over IP this was not a
big issue as although flags can have parameters, this was hardly used
until the flags for IP and E-mail protocols came into use. The new
flags however van have one or two optional parameters: an address,
host name or e-mail address and or a port number. A decent flag
checker programme should of course check the validity of the
parameters as well. And not just their validity if present, but also
if the required information to make a connection is present. A line
with a lone IBN flag and no hostname or IP address in the system name
field or another field holding a default value should be flagged as an
error.
My first step was to write a subroutine that could determine if a
strings is:
1) a valid IP quad or:
2) a valid fqdn (Fully Qualified Domain Name) or:
3) a valid IPv6 address or:
4) A valid e-mail address or:
5) a valid port number.
Two more classes of flags entered the scene. IPGLAGS end EMAILFLAGS.
The syntax for an IPFFLAG is
FLAG[:<hostname|ip-quad|ipv6address>][:portnumber] and for an
EMAILFLAG: FLAG[:emailaddress][:portnumber].
So in the config this was added:
IPGLAGS IBN,IFC,IFT,ITN,IVM,IP
EMAILFLAGS IMI,ISE,ITX,IUC,IEM,EVY,EMA
Implementing all this was a major operation that required a complete
overhaul of the flag check routines. Not only the flag fields
themselves had to be checked, but also other fields that can contain
default values for the parameters. To show some initiative I added the
feature of letting flags inherit parameters from previous flags in the
FIDONEWS 24-05 Page 4 29 Jan 2007
same class.
So IBN:fido.vlist.eu,IFC,IFT:fido2.vlist.eu would mean the same as
IBN:fido.vlist,IFC:fido.vlist.eu,IFT:fido2.vlist.eu
Summarising, I had now defined five classes of flags:
1) Normal class flags, no parameters used
2) User class flags, no parameters.
3) Ip class flags, two optional defaultable inheritable parameters
4) email class flags, two optional defaultable inheritable parameters.
5) Flags that are explicitly excluded although defined by implemantion
by one of the other four.
Default port number is of course the default port for the protocol in
question and default parameter # 1 is inherited from the system name
field, or the telephone number field.
Then someone who said "I am not a programmer but..." proposed to put
the default connection information not in the system name field, but
in the field destined for the location, separated from the location
itself by a # character. And it found its way into the nodelist.
Sigh..
I felt uncomfortable about it - Yet Another Method of listing IP
nodes- and the use of the '#' character conflicted with a recently
submitted proposal for listing IPv6 information of the nodelist, but
alas, it was not too hard, so a few more lines were added to my flag
checker routines. But I was getting a bit tired of it. Also my
programme was getting a bit too big for my taste. I was a bit worried
it would become top heavy...
But still the concept of different classes of configurable flags that
each had their own specific syntax and things to check remained. As it
turned out, my efforts to implement that particular way of listing IP
nodes was a wasted effort. It is no longer in use. Not an incentive
really...
And then someone invented the INA flag. Again a politician, not a
programmer. The INA flag should hold the default value for the connect
info for IP flags. It should end all discussion about where to put it
and appease those who refused to give up the BBS name in field 3.
I tried to fit it in, but found I could not without almost starting
all over again and without sacrificing the concept of configurable
classes of flags. I could not fit it in in any of the existing
classes. The INA flag requires one and only one parameter. The other
flags have either none, or two optional parameters. Also, the INA flag
does not stand on its own, if there is no IBN flag or other IP flag,
the presence of the INA flag is an error condition. So I would have to
add a new class just for this flag alone. Adding a class for a single
case almost boils down to hard coding a flag, something I wanted to
avoid.
Top it off with the added complication that there is no requirement
that the INA flag be listed before any other IP protocol flags, so
FIDONEWS 24-05 Page 5 29 Jan 2007
that in my particular case, I would have to add a separate pass while
parsing the line to extract info from the INA flag, before parsing the
other flags. All the more frustrating is that had it been proposed
five years earlier, I would have started on a different track and
implemented it without much problems. As it is, it just does not fit
in with what I already have. That annoys me.
In the old days, it would go like this: a programmer would write
something into his programme and when people started to use is, the
nodelist clerks would enter the flags needed to support it, into the
nodelist. Programming was fun. It also ensured that by the time a flag
or another feature reached the nodelist, it was always clearly and
unambiguously documented what it was supposed to do. Nothing is as
nitpicking as a computer when it comes to being told what something is
supposed to do. Any ambiguity will be severely punished.
Now, it is the other way around: FidoNet has been taken over by the
politicians. People who by their own admission "are not programmers,
but..." invent nodelist flags. With no regards whatsoever for the few
remaining programmers. How the programmers implement it, is their
problem. No matter how illogical it is or how ill if fits into what
already exists. Programmers are not consulted. The FTSC is not
consulted. When programmers speak up to vent their objections, they
are ignored. With the result that programmers who have retired from
programming for a living, and who now do it for the fun of it, find
themselves in the same position as when they were still paid for it.
They have to dance to the tune of the customers and the managers. With
the difference of course that they do not get paid any more.
People are afraid that with the few participants we have, changes will
drive people away. If people are forced to change node number, they
will leave they say. But nobody is concerned about an even smaller
group: the programmers. What about them? Should it not be an even
greater concern not to piss off and drive away the programmers by
political decisions that force them to do major rewrites or just throw
in the towel?
(c) 2007, Michiel van der Vlist. All rights reserved.
Permission to distribute via the Fidonews file echo
and the FidoNews echomail conference.
-----------------------------------------------------------------
FIDONEWS 24-05 Page 6 29 Jan 2007
=================================================================
ROBERT COUTURE'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://2f.ru/binkd/
| | maloff@corbina.net
| | v0.94 on Jul 24th 2000 (Outdated)
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 RC2 on Sep 22nd 2003
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
| | Martin_Junius@m-j-s.net v4.4.10
FIDONEWS 24-05 Page 7 29 Jan 2007
FMail |T |http://fmail.nl.eu.org
| | support@fmail.nl.eu.org v1.60
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://ezycom.sytes.net
| |http://members.westnet.com.au/centuryp/
| | ezycom@westnet.com.au 3:690/682
| | v2.0 on 3 May 2003
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
| | v3.6 on Aug 20th 1999
FIDONEWS 24-05 Page 8 29 Jan 2007
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
| |http://www.apoint-mail.de/indexe.htm
| | (English Version)
| | dirk.pokorny@apoint-mail.de
| | v1.25 2:2426/1210.13
FIDONEWS 24-05 Page 9 29 Jan 2007
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://mik.nu/golded-plus/ 2:203/6600
| | 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
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
GiGo |UI |http://www.gigo.com
| | v0109 on Jan 9th 1997
Internet Rex: |UI |http://members.shaw.ca/InternetRex/
Charles Cruden | | telnet://xanadubbs.ca 1:342/806
(Khan Software) | | v2.29 on Oct 21st 2001
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)
Ifmail |UI |http://ifmail.sourceforge.net
| | crosser@average.org 2:5020/230
| | Ifmail is a FTN <-> E-Mail/News Gateway
| | Program.
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.
MakeNL |U | http://hub2000.darktech.org/makenl
| | fidonet.hub2000 [at] gmail [dot] com
FIDONEWS 24-05 Page 10 29 Jan 2007
| | Fido: 1:229/2000
| | FidoNet Nodelist Processor
+- - - - - - - - - - -+- - -+- - - - - - - - - - - - - - - - - - - -+
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: Robert Couture, 1:229/2000
E-Mail: rpa4email (at) rogers (dot) com
Telnet: runekeep.darktech.org
(Leave Feedback as Guest or create an account)
Emeritus: Ben Ritchey, Todd Cochrane, Frank Vest, Peter Popovich
-----------------------------------------------------------------
FIDONEWS 24-05 Page 11 29 Jan 2007
=================================================================
SPECIAL INTEREST
=================================================================
Nodelist Stats
Input nodelist nodelist.026
size 644.7kb
date 2007-01-26
The nodelist has 5342 nodes in it
and a total of 7198 non-comment entries
including 6 zones
45 regions
324 hosts
364 hubs
admin overhead 739 ( 13.83 %)
and 637 private nodes
219 nodes down
261 nodes on hold
off line overhead 1117 ( 20.91 %)
Speed summary:
>9600 = 450 ( 8.42 %)
9600 = 4144 ( 77.57 %)
(HST = 81 or 1.95 %)
(CSP = 0 or 0.00 %)
(PEP = 1 or 0.02 %)
(MAX = 0 or 0.00 %)
(HAY = 1 or 0.02 %)
(V32 = 2107 or 50.84 %)
(V32B = 123 or 2.97 %)
(V34 = 2864 or 69.11 %)
(V42 = 2384 or 57.53 %)
(V42B = 135 or 3.26 %)
2400 = 37 ( 0.69 %)
1200 = 5 ( 0.09 %)
300 = 706 ( 13.22 %)
ISDN = 378 ( 7.08 %)
----------------------------------------------------------
File Req Flag Applicable software Number of systems
----------------------------------------------------------
XA Frontdoor <1.99b 1599
Frontdoor 2.02+
Dutchie 2.90c
Binkleyterm >2.1
D'Bridge <1.3
TIMS
Xenia
--------------------------------------
FIDONEWS 24-05 Page 12 29 Jan 2007
XB Binkleyterm 2.0 7
Dutchie 2.90b
--------------------------------------
XC Opus 1.1 2
--------------------------------------
XP Seadog 2
--------------------------------------
XR Opus 1.03 25
--------------------------------------
XW Fido >12M 215
Tabby
KittenMail
--------------------------------------
XX D'Bridge 1.30 2182
Frontdoor 1.99b
Intermail 2.01
T-Mail
--------------------------------------
None QMM 1310
--------------------------------------
CrashMail capable = 1937 ( 36.26 %)
MailOnly nodes = 2996 ( 56.08 %)
Listed-only nodes = 439 ( 8.22 %)
Other = -30 ( -0.56 %)
[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/208]
-----------------------------------------------------------------
FIDONEWS 24-05 Page 13 29 Jan 2007
=================================================================
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 24-05 Page 14 29 Jan 2007
Send articles via e-mail or netmail, file attach or message to:
Björn Felten
Fidonet 2:2/2
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 24-05 Page 15 29 Jan 2007
Credits, Legal Infomation, Availability
+ -- -- -- -- -- -- -- -- FIDONEWS STAFF - -- -- -- -- -- -- -- +
| |
| Editor: Björn Felten, 2:2/2 |
| Columnists: Frank Vest - Frank's Column |
| Thom LaCosta - Fidonet Related Websites |
| Robert Couture - Fidonet Software Listing |
| Daryl Stout - Telnet BBS Guide |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
+ -- -- -- -- -- -- -- - 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 is 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.
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: |
| current issue FIDONEWS |
| back issue, volume v, issue ii FNEWSvii.ZIP |
| |
| On the web: |
| http://felten.yi.org/fidonews |
| http://www.fidonet.ca/fidonews |
| |
| The Snooze *and* the FIDONEWS echo in your newsreader: |
| news://felten.yi.org/FIDONEWS |
| |
+ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- +
-----------------------------------------------------------------
Download original FidoNews · Volume 24 (2007) · ← Previous · Next →