Order Tray | Contact Us | Home | SIG Lists

[aprssig] Worst Path of the Day

Wed Oct 27 14:48:42 UTC 2004

The problem is that user education is not working.  Yes, in a number of
the cases out there it will because someone doesn't know any better and
are willing to listen.  But I have a "guru" in my area that is actually
telling people to setup their digis and trackers improperly and when I
try to educate nothing changes because they have already been educated
(kinda) (he said...).  And then the others out there that know better
than the rest of us aren't going to change anything "just because".

What we need is the big stick to let these folks know that it is not
okay to use these kinds of paths.  And I don't buy the "well in an
emergency" line either.  You shouldn't be trying to make APRS go outside
of your ALOHA circle.  With dynamically set paths (as I suggested
earlier) this would keep the stations within their circle where the
interference and collisions are "manageable".  Just because you have an
emergency doesn't mean that APRS is going to work any better and trying
to force it only makes things worse.

kf4otn at amsat.org

Project OSCAR Member
AMSAT-NA Member: 35360
AMSAT Eastern North Carolina Area Coordinator

-----Original Message-----
From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Steve Dimse
Sent: Wednesday, October 27, 2004 10:25
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Worst Path of the Day

On 10/27/04 at 8:06 AM Robert Bruninga <bruninga at usna.edu> sent:

>I like this one.
>Getting to the internet is easy and easy to fix.
>It is easier to put up an IGate than a digi.
>Let FINDU not show anyone with a path longer than 3.

Besides the fact that findU does not currently parse out paths because
they are irrelevent to its mission, all this does is shift the burden of
educating wayward users from the entire APRS community to me. When a
page doesn't show, I'm the one that would get the email from Joe Ham, or
worse his wife or kids, I'm the one that would need to explain things to
them. I do not have the time or inclination to do this.

I am short of time now, and cannot implement path parsing at this time
in any event. At most, IF someone creates a clear, concise web site
explaining why excessive paths are bad, including instruction on how to
fix them in all the popular APRS programs and trackers, then at some
point when I have time, I'll add parsing, and place a notice on the web
page with a link to the educational web site. A person or group would
also need to volunteer to be the contact to handle all questions on this
that do end up directed to me.

I won't be the APRS path cop, but I am willing to help.

Steve K4HG

aprssig mailing list
aprssig at lists.tapr.org

More information about the aprssig mailing list