Normally I wouldn't share Fido stuff in an Othernet, but if you
currently reside in what is known as "region 11", IL, IN, KY, MI, OH,
WI... this will shed some light as to the current situation if you
are having troubles obtaining a node number in that area:
Most important thing is to keep the idea of geographical regions alive. This
how fidonet always worked. No? There were no mandatory geographical regions
the beginning? Anyway, it is in the POLICY and there is no way to change it
If a technically-competent person cannot be found to be RC, the region
can be merged with another. There is no gun to my head that I must keep ten different RC's in the zone 1 segment. The RC assignment or removal
has no technical impact on a Sysop's node number. If other RC's agree
then its done.
On 27 Mar 20 09:50:36, Oli said the following to Atreyu:
Most important thing is to keep the idea of geographical regions
alive. This how fidonet always worked. No? There were no mandatory
geographical regions the beginning? Anyway, it is in the POLICY
and there is no way to change it
I get all warm-n-fuzzy when you write the word policy in all
uppercase... as if to assert your superior knowledge over that
clueless redneck dumbass ZC1.
I assume this is for me not taking your troll-bait in FSX_GEN some
time ago.
Its really nice and pretty to have geographical regions to seperate
nets into, but the vanity has long faded and the RC position is that
of a traffic-cone.
Its just there to direct people where to be listed.
I assume this is for me not taking your troll-bait in FSX_GEN some
time ago.
Btw, congratulations for fixing the missing REPLY kludge in the software tha you use on FSXNet as a reaction to my "troll-bait" (but maybe you are talkin about other delusions).
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 108 |
Nodes: | 16 (0 / 16) |
Uptime: | 01:47:16 |
Calls: | 5,715 |
Files: | 8,496 |
D/L today: |
14 files (1,320K bytes) |
Messages: | 339,192 |