T h e F i d o G a z e t t e! Volume III number IV June 2009
+--------------------------+------------------------------------------+
| .----------------------. | dr.debug: dr.debug @ filegate.net |
| | A monthly E-Zine | | bbslists: bbslists @ filegate.net |
| | published by Fidonet | | articles: fidogazette @ filegate.net|
| | to promote BBSing | +------------------------------------------+
| | ____________. | |
| | / __ | "Anyone who has never made a mistake |
| | / / \ | has never tried anything new." |
| | WOOF! ( /|oo \ | Albert Einstein |
| \_______\(_| /_) | |
| \@/ \ | Got Something To Say? |
| .---.\ _ | Say it in the |
| (jk) _ |usb| \ \\ | =The FidoGazette= |
| / | .___. \ ))| |
| / | /_ | / \// | Editor: Janis Kracht |
| |___| // || _\ / | janis @ filegate . net |
| .--`-. (_|(_|(____/ | janis kracht 1:261/38 |
| |____| (jm) | |
+--------------------------+------------------------------------------+
=======================================================================
==-=-=-=-=-=-=-=-=-=-=-=Contents=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=======================================================================
T h e F i d o G a z e t t e! Volume III number III May 2009
=======================================================================
Editorial:..................................................(1)
New Members/In the Works/Returning Members.................(2)
The Slightly Crusty Sysop..................................(3)
The Old School Toolbox: Bots Part 3........................(4)
FidoGazette BBS List.......................................(5)
Dr.Debug Answers Your Questions............................(6)
A hardy Net 261 Welcome....................................(7)
Food.......................................................(7)
The New Age Haunts Some....................................(8)
Info (Where to Send Articles)..............................(9)
Page 1
T h e F i d o G a z e t t e! Volume III number IV June 2009
===================================================================
Editorial
=========
Thanks to two people who are now contributing here and will be on
a monthly basis, we have a crew of three writers now. That is
something to me and I'm incredibly thankful to you fellows.
Richard Webb is continuing his "ToolBox Series with Part #3", and
this month Sean Dennis returns to the Gazette with his own
by-line and column, see "Slightly Crusty SysOp", which I think is
fantastic. I may not always agree with him but we agree often
enough I think (smile) and I'm really happy to see him involved
again! Who knows.. maybe I'll call his house when he's at work
and get Maura involved when he's not looking (gd&r)
Thanks to both of you, greatly appreciated!
The GamesCorner had to take a break from including the Crossword
Puzzle this month.. Didn't have the time to do the graphics for
this issue. The puzzle is done though so it will be faster or
the next issue :)
Page 2
T h e F i d o G a z e t t e! Volume III number IV June 2009
=================================================================
New & Returning Members
=======================
By Janis Kracht
New SysOps -- Welcome to Fidonet!
=================================
No apps received.
In the Works:
=============
Region 11: Gordon Meyer
=================================
Returning SysOps - Welcome Back!
================================
Region 13: Scott Knapp
Region 18: Michael Aurelio
The Slightly Crusty Sysop
By Sean Dennis, 1:18/200
I guess I should introduce myself if you don't know who I am
already. I'm Sean Dennis, the original editor of the FidoGazette
and a longtime (over a decade now) Fidonet sysop. I'm also a
former R11C. As the former FidoGazette editor, I was
castigated by several of the Fidonet "elite" by daring to create
an actual, useful newsletter for Fidonet instead of the empty and
pathetic shell that Fidonews is now due to anti-American views of
the uber-liberal and arrogant Zone 2 sysops. Not all Z2 sysops
are complete jackasses, but it seems the few that are tend to be
like a zit on your face on prom night: you know it's there, you
want to take care of it, but you dare not do it lest someone else
finds out and makes fun of you for doing so. So, I am back
involved peripherally with the FidoGazette, providing an opinion
column for the ol' FG, just because I can.
As you can see, I'm quite opinionated, but I try to be fair with
my opinions- meaning I treat everyone equally. My goal in this
column is to bring Fidonet related issues to light and issues
that are related to Fidonet, be it socially, politically,
technically or round-about-ly.
I'd like to thank the current editor of the FG, Janis Kracht, for
letting me have a column in this fine publication (not that I'm
biased or anything).
The current issue that I'd like to poke a stick at is Fidonet's
slow but eventual death due to the cancer within. As you can see
by my rather blunt views above, perhaps a cloud of an idea may
begin to form about the "cancer" I speak of. The Internet didn't
kill Fidonet as Richard Webb so succinctly put it - Fidonet
killed itself with its members' arrogance, pedantic ways and
general rudeness.
I've talked to several young and up-and-coming sysops who say
they will never, ever join Fidonet. Why? Because Fidonet has a
reputation for being a nasty place to be - unfriendly, cold and
generally unpleasant. Now those of us who have been around in
Fidonet for some time know that is not always the case, but it
seems that we, Fidonet, have cultivated a maelstrom of
unpleasantness that has seeped outside of the network and
tarnished our collective reputation.
If you've ever taken a look to see inside the FN_SYSOP and
FIDONEWS echoes, you can see what I talk about. It's a culture
war in those echoes and well, folks, the writing's on the wall --
if we don't change the pedantic and inane ways of some of the
Fidonet "administration" as well as get rid of the undesired
trash in Fidonet, someone's gonna have to turn the light off
after everyone's gone.
A lot of the unpleasant people have left Fidonet, but there are
still quite a few -- more than our fair share's worth -- pedants
hanging around. I'm not going to name names, of course, but you
know who I'm talking about. Of course, if you talk to some
people, I should be out of Fidonet, but hey, after twelve years,
I really don't care what some people think. I seem to have
plenty of Fidonet-friends in high and low places and I've learned
to avoid such cesspools of filth (read: particular echoes).
Seems to make my time reading mail a lot nicer too knowing that
some dimwit isn't going to try to shove his verbal masturbation
on me.
But for all the nastiness, there are some bright spots in
Fidonet. I know of several echoes that are pleasant,
light-hearted and still a valuable place to gather online. Yes,
Fidonet (and BBSing in general) doesn't offer the "instant
gratification" that a lot of the younger Internet-weaned
generation wants, but in a lot of ways, that's better. These
kids wouldn't know their head from a hole in the ground...and
we've got enough of those grown-up kids polluting our echoes as
it is.
What can we do about this cancer creeping in, killing Fidonet?
Some suggestions:
* Act our age, not our shoe size.
* Remember the old saying "insert foot, echo internationally".
* Agree to disagree. It's hard -- especially for me -- but it's
got to be done if we're going to get along.
* Remember that Fidonet is an exercise in anarchy and not in an
oligarchy.
* Together we stand, divided we fall, alone we make fools of
ourselves.
* Prove to the next generation of sysops that Fidonet is a good
place to be and that it is worthy of their care and attention
so it can live on for another quarter-century.
* Show that the Internet is not the only place for social gathering
that can be enjoyable.
Anyhow, just my thoughts on this subject. If you'd like to give
me your thoughts, please netmail me at 1:18/200 (preferred) or
email me at sean@nsbbs.info with the subject of "Crusty
Feedback".
Oh...the column name? Well, it comes from the fact that as I've
gotten older, I've begun to get a little crusty: more anti-social,
more cynical and generally more of a malcontent with people. I don't
really hate people -- I just think that people think of themselves
too much and don't realize how they look in other people's eyes.
Standard disclaimer: the views expressed in this column are of
me, Sean Dennis, and not of the FidoGazette, its editorial staff
nor anyone else (like anyone really would want to share the same
views as me, right?). I assume all responsibility for screwing
up facts, stretching the story a bit or just telling it like it
is.
Page 3
T h e F i d o G a z e t t e! Volume III number IV June 2009
===================================================================
The Old School Toolbox
By Richard Webb, 1:116/901
Bots, Pt III.
In this installment we'll look at those that generate
messages automatically. This is usually a sysop's first look at
automation, other than areafix and the standard file request
we've all come to know and appreciate.
So, who needs additional automation over and above that
provided by their favorite ftn mail processing? THe busy sysop
that isn't around to check his board as often as he'd like to
validate new users. THe echo moderator might wish to send
updates to the echolist or other echo listing database, as well
as post rules in the echo.
I have a good fidonet friend who is an echo moderator. HE swears
he'll never resort to automation to update his echo's listing
with the echolist, and won't use it to post rules or send
messages. HE feels that there are enough fidonet systems just
chugging along on autopilot out there and his point is valid.
YEt, for some of us, automation serves many purposes. SOme of the
most common are:
Posting statistics on a regular basis to a local or echomail
area;
Posting announcements or bulletins;
Posting captured output of diagnostic or maintenance processes
for later review.
First let me give you a glimpse of how I use them, then we'll
talk about some of the tools I use, and which tools I like for
given applications.
Of course I send my updates to the echolist without even
being present. THey go out bright and early on the appointed day
while I'm still snug in my bed. NO reminder needed, etc.
I'm involved in a ham radio network which requires that net
control stations turn in monthly reports of the hours they worked
controlling the net, whom they handed off to, etc. My automation
happily parses my station log files and sends said report to the
net manager via email on the first day of each month, again while
I'm tucked in my bed.
I moderate four echoes. All four see rules postings on a
regular basis, and all of these are done via automation. IF my
machine saw an unscheduled reboot that indicates a power outage a
message is sent to me. Also, when I'm away from home my system
sends a couple of friends messages letting them know it's still
alive and kicking. ONe friend knows that if I'm out of town and
he doesn't see messages for two or three days he's to call one of
two or three phone numbers and ask the party on the other end to
please check out Richard's house.
If you recall in the first part of this series I discussed some
of my automatic response features that I've set up to run from
artware's netmgr. ONe I mentioned was my nodelist lookup tool,
good for that echo moderator who isn't a fidonet sysop (grin).
THe nodelist lookup tool requires one of these automatic message
posters to return the actual results to the requester. This is
because the nodelist lookup batch could not run on a command
shell from netmgr, as this batch requires copious use of
environment variables, a lost resource to later windows users.
Hence, the nodelist lookup requires that the batch which netmgr
invokes on a command shell set up the autoposter to return the
message to the proper individual at the right address.
There were many tools developed back in the halcyon days of
fidonet to accomplish automatic posting of messages. Some were
bundled in with software developed for other purposes. OThers
were stand alone programs designed specifically for this purpose.
IN this installment of the toolbox we'll have a look at message
posters only.
All of these have one feature in common. THis is the ability to
post any text file. some impose size limitations, and others have
further limitations. FOr my applications I've found myself using
more than one in the past.
Just as your tool kit should contain a variety of
wrenches and screwdrivers I've found that some autoposting tools
are better suited to certain applications. SUre, you can use one
of those adjustable wrenches for just about any nut, but if
you're not careful with them or the vise grip type tools you can
do damage to the fastener you're working with. HEnce, the proper
wrench is always a better fit.
In my earliest days as a fidonet sysop I discovered Harvey
Parisien's robot, available from many systems still as
robot600.zip which is quite versatile. Harvey's robot had several
nice features, and I'd already registered my copy of professional
point, so I became conversant with it fairly quickly. THe robot
worked from standard text files and came with plenty of samples
to show one how to utilize it.
Harvey's robot required you to fire packets into your
inbound or outbound directory however. IF you wanted the messages
to show up in your message bases you would need to fire them into
your inbound directory and show an address that your mail tosser
would accept. I configured some dummy points in my private
addition to the nodelist just for this purpose, and away we went.
I soon figured out some of the limitations however. Harvey's
robot works nicely with netmail and echomail, but local message
areas on the bbs couldn't be touched by it without some kludging.
Also, you had to build a robot configuration file for every job
that you might want to use an autoposter for.
Still I lumbered along in all my days of fidonet, using netmgr
masks to toss inbound netmail from the robot to local message
areas on the bbs when necessary. Still, I found myself with a
whole directory of these little 2-4 line .h files.
To make matters worse, my main batch file became quite
unwieldy for days such as the first of the month with all these
firings of the robot, the invocation of pktdate to fix y2k
problems in Harvey's robot, and then an import round from my mail
processor. THen because some of this was email through the gate
and netmail I'd want netmgr to strip off the point address, so
then the mail processor did a round of exporting, lather rinse
repeat. ITs biggest weakness, and hence the unwieldy batch files
was the fact that one couldn't use a different "from" name for
every message. THOse little robot scripts all use the same "from"
name in every message they generate. want a different "from"
then build another robot script.
When I was first getting hooked up as a fido sysop again
I was replacing many things I'd lost in hurricane Katrina,
including just about all of the software I used in the glory days
of my bbs activity.
A friend of mine kindly sent me a copy of Harvey's robot, and
another nifty little thing called postit.
Being the type that isn't up for a lot of adventure when it
comes to getting computer stuff working I went with the devil I
knew when setting up my system. Harvey's robot dutifully posted
rules in the echoes I moderate; sent out echolist updates which
my processor dutifully killed after sending and life was good,
except for those unwieldy batch files. MORe stuff got added (the
radio network reports mentioned above among them) and my first of
the month section of the batch file now required its own batch
file. even with the simplification offered by postit the darned
thing is still pretty big. to accomplish everything that I
require on the first of the month there are nearly 700 lines,
counting remarks. IT was half again as big before I decided to
give postit a spin.
The "from" name limitation was what I bumped up against first
when looking at the jobs I wanted done by an autoposter. IT was
time to take a serious look at other tools. Before I got to
postit I had decided to have another look for something to handle
areafix functionality for me. Back in my busy system days I'd
used squalid as my areafix as it was the only one totally squish
compatible, but it had some limitations. NO autoforwarding of
requests, and rather bare bones in other ways. SO, I had a look
at sqafix.
Bundled with sqafix was a little utility called sendmsg which was
the author's way of providing for autoforwarding of requests
before such functionality was complete within the program itself.
IT allowed me to post to local areas as well, handled squish
format message bases directly, but still had some limitations.
Horses for courses: THe little sendmsg utility bundled with
sqafix didn't do origin lines properly for echomail, and this was
a problem for me. YEs I know, squish is supposed to take care of
that little detail, but I don't find it reliably picking up on
messages that do not have a valid origin line. THe message
posting functionality built into artware's netmgr seems to
truncate larger messages, and was not suitable for multipart
postings.So, back to the drawing board. IN addition to the from
limitation of Harvey's Robot there's also the problem of y2k
compatibility. Easily fixed with pktdate, but we were trying to
streamline the batch files, part of what this whole exercise was
about.
So, another look at postits docs. Hmmm, command line syntax
examples didn't look too cumbersome, so I gave it a test spin on
a couple of my local areas. I liked the fact that it supports
*.msg, squish jam or Hudson message bases directly. I'd seen
enough of these things that supported *.msg and maybe one other
message base format, but this one supported most of the major
players in the message base format game. Even though I wasn't
planning on changing message base types, it was nice to know I
had the option to continue using the same tools should I decide
to for other reasons.
Then I discovered its best feature for the way I work.
INstead of invoking postit multiple times as would be required on
the first of the month, just put all those commands in one file,
invoke postit once. YEs, this required registration, but a $10
bill for something that useful isn't much. SO off went a check
for ten bucks.
The robot only allowed one from field for all the messages it
posted during that invocation, whereas postit allowed me to
define a separate from and "to" field for each. I could have a
bulk file set up to post a message to the echolist showing my
name in the "from:" field, "echo moderator" in the rules posting,
"Joe sysop" in another if I chose, etc. RIght up my alley!Even
better, custom origin lines are supported!
Even better yet, no product brag line. YEs you can look at the
usually hidden control lines and find out which software was used
to post a message, but there are times I'd as soon use something
to respond or provide information where I could easily just post
an already created text file. Now you're asking yourself why I
just don't open the required text file with my favorite text
editor and do a straight reply, pasting the text into said reply.
Hmmm, I know I've got the file with the info you asked for, but
first I've gotta find it. But, now that I've located that
blasted file I don't have time to open my message reader, find
your message, paste the text, etc. But, I recall your name and
fido address, or made a handy note. SO, while I recall the path
to that file, I bang out a command line for my autoposter causing
a message to be generated going back to you. The message goes
into the proper area and is scanned out next time, and I'm off to
do whatever else I need to accomplish. IF on the other hand I do
one of those "I'll have to take care of sending that when I get
back home things I might forget, and you'll wonder after a day or
two if I am ignoring you or something even more unflattering.
Why do I wish to post an already created text file? Lots of
reasons may occur to you. Alright, another example. I get
bulletins from the American RAdio relay league, and a variety of
other ham radio related electroniic publications which I post to
relevant echoes. Some of them need to be broken into parts to
accomodate the variety of echomail processors in use. Creating
robot scripts depending on how many parts the publication
required was cumbersome when writing batch files. A simpler
method was needed, with provisions to inform me that the
publication in question required more parts than I provided for,
and therefore was not posted, and the resulting files created not
deleted.
So, after soldiering on with the tools I knew how to use for
awhile I thought it was high time to have a look at something
else and see if it met my needs. Another friendly fidonet sysop
and ham radio aficionado could forward me some items I can't
access from the web at another email account, but he found
preparing them for transmission as echomail cumbersome. I agreed
to prepare them for transmission as echomail if he'd be willing
to send along those I couldn't access. Suddenly my comfort zone
of the familiar and known had to be invaded, for it was time to
try something new.
Yes, I still use the robot for some posting chores, and the
automatic posting facilities in netmgr for others. BUt, it seems
I've found my autoposting version of the adjustable wrench,
finally after years of looking. SO, we've had a good look at some
common fidonet bots. NExt time, we'll have a look at fidonet
mailer types, how they differ and how they handle traffic and
other housekeeping.
Upcoming: Want to increase your wireless networking range?
Yes VIrginia, it's old school, it's radio! THink before you part
with your $$$ and try a couple of experiments first! Maybe
you'll see some benefits, and maybe you won't. Free upgrades are
always the best upgrades, so give these a try first.
Page 4
T h e F i d o G a z e t t e! Volume III number IV June 2009
===================================================================
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
!!! G A Z E T T E B B S L I S T !!!
=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-==-=-=-=-=-=-=-=
By bbslist @ filegate.net
Send updates, changes to address above or to janis @
filegate.net.
System.......Prism BBS
FidoAddress..1:261/38
Phone........607-655-5652
Software.....BBBS LiI Flag
OS...........Linux (Gentoo)
C/B Verify...None
Access.......First Call access to Msg bases,
and file areas.
Telnet.......filegate.net
telnet access offers full features
of the standard bbs such as doors,
qwkmail, BWmail,Files, etc.
www:.........http:/www.filegate.net:8090/bbbs
[web interface is limited really
to reading messages and replying
online, or downloading messages
in qwk packets, but not uploading
them], and file download access.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
System.......Time Warp of the Future BBS
FidoAddress..1:14/400
Phone........none
Software.....sbbs 3.15a (very beta)
OS...........win. (xp pro. sp3)
C/B Verify...None
Access.......First Call access to Msg bases, and file areas.
Telnet.......time.synchro.net:24 or time.darktech.org:24
or timewarpfuture.dyndns.org:24
telnet access offers full features
of the standard bbs such as doors,
messages or file area etc.
www:.........http://time.synchro.net:81
Web interface is limited really
to reading messages and replying online, or
downloading messages in qwk packets, but not
uploading them, and file download access.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
System.......Lionsden BBS
FidoAddress..1:224/303
Phone........613-392-8896
Software.....Sunchronet
OS...........Windows XP
C/B Verify...None
Access.......First Call access to Msg bases, and file areas.
Telnet.......lionsden.darktech.org
telnet access offers full features
of the standard bbs such as doors,
qwkmail, Files, etc.
www:.........http:/www.lionsden.darktech.org
You will redirected to a menu where you can
choose one of three sites. The first one is
private and requires PW to get into.
FTP..........FTP://lionsden.darktech.org Files only
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
System.......Christian Fellowship
FidoAddress..1:266/512
Phone........1-856-933-7096
Software.....PCBoard 15.3
OS...........Windows XP pro
C/B Verify...Manually via email or voice
usually within 24 hours.
Access.......Read only
until verified. Once
verified write access
to Msg bases, file
areas, chat and
doors/games.
Telnet.......cfbbs.dtdns.net
or cfbbs.no-ip.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Page 5
T h e F i d o G a z e t t e! Volume III number IV June 2009
===================================================================
=================================
Dr. DeBug Answers Your Questions!
=================================
By dr.debug @ filegate.net
What is a File Request?
=======================
A file request is a special type of netmail that allows you to
ask another Fidonet system for a file that system has in it's
filebase archive. Your mailer then picks up the file you asked
for and delivers it to your system.
If the system you are calling doesn't have the file you are
asking for, you will get an error message explaining that. If
there is some other problem (not enough time before an event, not
enough security, it's during ZMH, you need certain privileges for
that file, etc.) you will get a response explaining the problem
as well.
How to do it:
============
You send a message to the SysOp of the BBS who has the file, with
the name of the file you want in the Subject line, but you turn
on the FREQ bit of the message. That is what tells his/her
mailer to send you the file in the subject line. Different BBS
programs and mailers may do this a bit differently, but
essentially, they all have you set some type of "freq" bit or
flag so that the receiving system automatically knows that the
information you are sending in your netmail message is a
"request for a file to go from your system to mine please"
For instance, BBBS's mailer has you set the freq bit in a netmail
message in the Subj: line by prefacing the Subject: with the
character "&<".
Let's say I want to file request a file from Sean Dennis's
system. A file request from my system to Sean Dennis's system
would look like this:
To: Sean Dennis
Subject: &< 1:18/200 FILES
When I send this message to Sean's system, his system will
respond with a file that contains a list of the downloadable
archives on his system _if his system is set up to allow file
requests_. Some systems may not be set up to do so, so you
should check first. Also the name of the file may really be
named allfiles.zip, or files.zip, so I'm counting on his mailer
using the magic name of FILES.
FILES is the magic name normally used by SysOps in Fidonet for
the list of all downloadable archives - so if you want to know
what files a SysOp has, try freqing FILES. If you get an error
message, check the error message out, because the error message
will often tell you what MAGIC names the sysop uses for files
like the "allfiles" list.
So now you have the file list, you can peruse it at your leisure
and find that file you needed for your door tournament, etc. :)
Be prepared for a large file though.. some allfiles lists can be
large. The one at PRISM at one time reached 8M.. right
now it is at 3.7M because of drive crash a long time ago (grin).
Some systems may require a password for a particular file or
directory. To specify the password for a FrontDoor System, you
would do it like this:
To: Sysop
Subj: ZanyFile.zip ! mypassword
( filename (space) and a '!' character on the subject line )
For BinkleyTerm (this is not BinkD, remember):
Press Alt-G from the Binkleyterm screen. It will ask you
"address to get from", then file to get, password to use.
Squish tosser is similar to all of the above:
SQUISH GET FILE.ZIP!MYPWD 1:261/38
So check your bbs or mailer's documentation - it's probably there
and easy to do.
Regards,
Doc
=================================================
A hardy Net 261 Welcome
Michael Luko, 1:261/0
As temporary NC for net 261, I proudly and hardily welcome
Scott Brown from Westminster, MD and the members of his BBS,
The Realms of Blue, to Fidonet 261.
Page 6
T h e F i d o G a z e t t e! Volume III number IV June 2009
=====================================================================
-=-=-=-=-=-
F O O D Even sysops have to eat!
-=-=-=-=-=-
By Janis Kracht, 1:261/38
This is another tiramisu - a bit different than the one I made
for the Fidonet Cooking Echo picnic. Mine was more authentic,
but this one will be easier to find ingredients to make it. One
of my relatives in New Jersey sent me this recipe. I could say
something, but I won't Lol :) Hey I was born in Jersey so stop
thinking what you are thinking :) :)
Mickalena's Tiramisu
Serves 10-12 people.
1 package ladyfingers
6 eggs,, separated
1/2 pint plus 1 Tablespoon heavy cream
1/2 cup sugar
1 teaspoon vanilla or almond extract
1 cup strong black coffee
1 square baking chocolate, grated into curls with large side of
grater
Place ladyfingers in a square dish, 13 inches X 9 inches, or 11
inches X 13 inches
Soak ladyfingers with coffee. Beat egg yolks for 5 minutes,
gradually adding the sugar. The egg yolks should look lemony in
color.
Beat the heavy cream until stiff, and then fold into the egg yolk
and sugar mixture.
In a separate bowl, beat the egg whites until stiff. Carefully
fold the egg whites into the whipped cream mixture. Add vanilla
or almond extract and stir gently.
Cover the lady fingers with this mixture. Cover with tin foil
and refrigerate 2 hours. Sprinkle with chocolate curls, and
serve.
Page 7
T h e F i d o G a z e t t e! Volume III number IV June 2009
=====================================================================
[Articles]
The New Age Haunts Some
By Janis Kracht, 1:261/38
In 1990, Fidonet's Randy Bush arranged to have the K12
educational network incorporated into Fidonet.
The K12 Network's affiliation with Fidonet offered worldwide
telecommunications for teachers, students and schools that were
not able to access the internet because of constrained budgets,
or because they lacked technical expertise to implement
higher-level access to existing telecommunications networks.
Using our FTN technology, schools were able to use a penpal
program to "promoting global awareness" and soon many schools
were part of the K12 network.
The K12 Network left Fidonet many many years ago. If I had to
guess, I would say it was probably around 1995 or so.
And here we are in the present.
But what happened to all those posts after the K12 network left?
Are they gone? Did they get dumped in the bit-bucket? You might
be surprised at the answer and give thought to anything you post
on the internet, anywhere.
A few weeks ago, a young woman contacted me asking for help,
because some _17_ years ago, at the age of 11, she had posted on
the K12 network as part of the pen pal program. She'd been at
her uncle's house way back then, and had been offered the use of
the computer.
Now those posts show up with her name and a funny fidonet node
number when she searches for her name on Google, and she'd need
the correct "user name and password" to remove them according to
Google.
It was a harmless day of fun at her uncle's house, she
remembers:
"Here, type something on this machine, and people will type back
to you." he'd said to her.
She told me how she remembers now how amazed she was then at this
machine - She remembered thinking, "People did indeed respond!
You could make friends and 'talk'"
So she wrote a note to a "penpal". She told her new friend her
name, her city, her brother's name, where they lived and her
hobbies and some other personal information. She forgot about
it.. she was 11 - Who thinks what you type to a penpal!
Now - remember when all those search engine wars were going on?
Bits and bytes were flying left and right as one service vied for
superiority over another with better content.. and content meant
buying archives... archives of what? you know it.. usenet.. which
is where the K12 network stayed after they left Fidonet.
And of course who ended up with usenet and K12, but GOOGLE..
Should anyone google for this young lady's name, chances are
quite a bit of personal information will be made publicly
available. This is not something she is very comfortable with.
And so, now and theoretically, forever, this young lady's
personal information will be on Google's groups and plainly
"available". She is lucky however, being Canadian. She at least
has a Privacy Commisioner where she lives, who may be able to
convince Google to remove the information because she was so
young when she entered the information.
It strikes me how much information we haphazardly enter into the
'infobalm'. People may not realize that places like FaceBook and
other similar 'social networking spots' may soon become the next
'collection' points - that is if they are not already - for
search engines and commercial marketing tools and ploys.
All of this brings to mind the words someone said to me long
ago (in about 1992 as I was taking over the PDN FDN), "Leave the
smallest electronic footprint you can".
It was my husband who said that to me then, and he was abolutely
right.
Page 8
T h e F i d o G a z e t t e! Volume III number III May 2009
================================================================
INFO:
Where to Send Your Articles
Unlike most editors, I surely do not mind running my mouth when
there is a sparcity of articles for the 'zine. I'd MUCH rather
you sent in material but I think until someone starts a
discussion you feel like commenting about, you evil dullards
(just kidding!!!) will no doubt complain about "no issues" (grin)
So I will fill these issues with my meanderings and thoughts and
hopefully we will grow into something of consequence here :)
Don't be offended.. write an article!
If you WOULD like to submit an article and prove me wrong about
the dullard aspect of you guys and gals (bg), feel free to drop
your article off at:
By email attach to address: janis @ filegate.net
Fidonet attach: Janis Kracht 1:261/38 Modem: 607-655-5652
1:261/100 filegate.net via telnet mailer
filegate.net via binkp mailer (don't send
articles as routed attaches, send them
direct to filegate.net).
Give it a title, sign your name and network address if you have
one and send it along!
Don't worry about the format, I can take anything you send me
and mutilate it further as you can see above. Linux is nice
that way (g). Spell checking your own work will help though
(something I'm typically guilty of (g)).
To send a question to Dr. Debug, email a question to
dr.debug @ filegate.net or post in the fidogazette echo! :)
To send a listing to the fidogazette internet bbs list, send your
bbs listing to bbslist @ filegate.net or post it in the fidogazette
echo! :)
Page 9
T h e F i d o G a z e t t e! Volume III number IV June 2009
=====================================================================