[aprssig] pointless text in the status (was: Preparing for a long roadtrip - VA)

[Robert Bruninga]

>>> w2pi at optonline.net 05/31/06 12:57 PM >>>
>Correct me if I'm wrong - but isn't part of the beauty of voice 
>alert that by transmitting with PL100, anyone listening with 
>their volume turned up and pl set will know you're there?

But that is -half- the problem.  It assumes the recepient is "listening".
As I posted before, of every new person I meet with a D700,
less than half have ever heard of "Voice Alert".  ANd half of the
half that have, admit "they dont understand it and have not
set it up"....

SO only 1/4th of the people that can use Voice Alert with a
simple front panel setting, do.  Hence, the need to indicate
that your radio -is- set up for VoA and ready...

>In this situation, you don't need anything in the status text - 
>its right there coming out of your speaker, if you're in range.

which assumes:
1) another D700 is in simplex  range 
2) He is also set for Voice Alert
which makes it extremely rare.

Better to include it in your status text or psoition comment
so that it reaches 100% of all APRS recepients within ALOHA
range which is about 100 times more than those that would
hear it otherwise...

de WB4APR, Bob

----- Original Message -----
From: Jason Winningham <jdw at eng.uah.edu>
Date: Wednesday, May 31, 2006 10:24 am
Subject: Re: [aprssig] pointless text in the status (was: Preparing for a long roadtrip - VA)

> 
> On May 30, 2006, at 11:34 PM, A.J. Farmer (AJ3U) wrote:
> 
> >  I just don't see the point in announcing it as part of your 
> status 
> > text.
> 
> That hits one of my pet peeves - pointless nonsense in the status 
> field.
> A personal message is fine, a town name or email address is great, 
> but 
> why in the world would station AB1CDE use "AB1CDE" as the status text?
> 
> UI-View's default status must be {UI-View a.bc} or some such.  If 
> UI-View uses the destination call correct, all that information is 
> already in the packet without wasting most of the status text 
> dispaly 
> on a D7 or D700.
> 
> Probably the worst is WinAPRS, which has program name, version 
> number, 
> and some abbreviated form of location that turns out to be just 
> garbage.  Here's an example:
> 
> WinAPRS 2.5.1 -ALDALOZARK   -251-<520>
> 
> OK, we're apparently told 3 times what version of WinAPRS is 
> running: 
> once in the destination call and twice in the status.  Maybe <520> 
> is a 
> build number?  Who knows.  what is ALDAOZARK?  some reverse 
> engineering 
> and map browsing will eventually tell you that this cryptic string 
> means the station is in Ozark, AL, Dale County.  The coordinates 
> in the 
> packet already gave me that information.
> 
> I'd like to be clear I do not blame users for the defaults that 
> the 
> _developer_ includes.  I'm certainly not picking on the station 
> whose 
> status text I copied (note I didn't include the call).
> 
> 
> Rant mode off.  Sorry, just couldn't hold that one in any longer. (:
> 
> -Jason
> kg4wsv
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org 
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig 
> 

_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org 
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig