| |
ZL3AI > APRDIG 17.11.03 11:48l 262 Lines 11051 Bytes #999 (0) @ WW
BID : 2294-ZL3AI
Read: GUEST
Subj: TAPR Digest, Nov 06, 3/5
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<IK1ZNW<IW7CHV<WA7V<
VK7AX<ZL2BAU<ZL3VML
Sent: 031117/0851Z @:ZL3VML.#80.NZL.OC #:13004 [Chch-NZ] FBB7.00i $:2294-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: DX cluster spots on APRS (the RIGHT way)
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 6 Nov 2003 14:10:34 -0500
X-Message-Number: 17
On 11/6/03 at 10:59 AM Scott Miller <scott@opentrac.org> sent:
>Very, very bad, to the point of bordering on malicious interference IMHO.
>Has anyone spoken to the person doing the gating? This is a perfectly valid
>application of APRS technology, but NOT something that should be on the
>primary APRS-IS!
As I stated I emailed him several times, even got my landlady who speaks
french to translate a detailed message for me, never got a response, which
was when I decided the only recourse was to filter his data from findU.
Steve K4HG
----------------------------------------------------------------------
Subject: Re: SSID Conventions?
From: "B. Hildebrand" <bhildebrand@earthlink.net>
Date: Thu, 6 Nov 2003 11:14:14 -0800
X-Message-Number: 18
The GPSxyz TO field can specify an Icon ( symbol ) for NMEA trackers, and
any SSID can be used, thus NMEA trackers are not limited to the SSID
specification for the Icon.
Brent KH2Z
----------------------------------------------------------------------
Subject: "Paths" ?
From: "Robert Mitchell / KD4PBC" <aprs@kd4pbc.net>
Date: Thu, 6 Nov 2003 15:04:13 -0500
X-Message-Number: 19
Hi All,
My tracker has been off for several months now. I want to reconnect it BUT
there is so much flying around About the path to use I need some help.
Before I had it set to relay, wide7-7 I was told that this would guarantee
that my location made it to the APRS-IS network.
Not only did it not always make it there but I got a few nasty emails from
people about the path. Just bitching mind you when I answered back and ask
for help with the correct path they had nothing to say.
I live in east Tennessee (Johnson City) and travel a lot around this part
of the country FL,NC,SC,KY,OH,TN,AL,VA,WV,LA,MS sometimes GA.
Is there a "one size fits all" path ? I run a KPC3+ with only a GPS input
so changing paths on the fly is not an option.
Contact me on list if this is useful to others otherwise off list.
Thanks,
Robert / KD4PBC
----------------------------------------------------------------------
Subject: Re: "Paths" ?
From: Kirk Mefford <kc2elo@softhome.net>
Date: Thu, 06 Nov 2003 14:36:45 -0600
X-Message-Number: 20
At 02:04 PM 11/6/2003, Robert Mitchell / KD4PBC wrote:
>Not only did it not always make it there but I got a few nasty emails
>from people about the path. Just bitching mind you when I answered back
>and ask for help with the correct path they had nothing to say.
>I live in east Tennessee (Johnson City) and travel a lot around this
>part of the country FL,NC,SC,KY,OH,TN,AL,VA,WV,LA,MS sometimes GA.
I can see why people would complain about the path you used to use. I can
see a bit of your problem going by the states you have listed that you
travel through. The problem with APRS is that it doesn't have total
coverage of the US and/or the world. I used to live in GA and recently
made a trip along I-20 to my new/old home of TX. Most of my trip did not
make it to any Igates and I had what several would consider a pretty
aggressive path setting of RELAY,WIDE3-3 .
If there isn't any digipeaters and/or igates in an area you aren't going to
make it to the internet no matter how large of a path you have. So that
WIDE7-7 path wasn't helping you in the areas with nothing and causing all
sorts of problems for the areas where there were several digipeaters.
Most areas I've been around, you will normally make it to an igate in 2-3
hops or not at all.
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: Re: DX cluster spots on APRS (the RIGHT way)
From: "Gregg G. Wonderly" <gregg@skymaster.cytetech.com>
Date: Thu, 06 Nov 2003 15:16:44 -0600
X-Message-Number: 22
>Personal attacks resume. Be nice just once to have a discussion on the sig
>without name-calling.
This is not a personal attack, just a point of reference of my feelings
about your attitude. You use sentences that do not include phrases like
'in my opinion' or 'I think' that are very declarative and absolute
sounding. That's why I chose those words.
>I stand behind my statement. As Bob admits, no one else has implemented his
>color scheme to display those three bits of information. The question is why!
>
>It certainly is not out of ignorance.
I have been writing APRS software using only the spec because that is the
standard and I have no way to run APRSDos, and thus have not downloaded it
and read through all of his personal documents. Thus, I am in fact
ignorant of a lot of these points specifically because of the fragmentation
of information created by everyone demanding that there be nothing about
the GUI be documented. There should have been appendices to the spec that
contained all of Bobs documents. There could have been a lot of
information clarified for many people if they could have, in fact, found
the the vast experience that Bob has with APRS documented with the spec.
But, alas, I can only suppose that you experts know the best and Bob's
experience and knowledge is just worthless to the rest of us. We'd have
nothing to learn from reading that information it seems.
>Bob has been pushing this since MacAPRS
>came out nearly 10 years ago, and early GUI APRS developers like the Sprouls,
>myself, and Brent all were APRSdos users first, if for no other reason than
>there was no other choice.
And these systems all had limitations as you specified below regarding
mapblast that restricted what you could do with APRS. Plain and simple,
the mapping systems you chose were not, at all, capable of doing the job
you needed. Sure, they show where stations are at with icons. But, that's
only a portion of the information available in APRS...
>I maintain it is because this is simply not useful to most users, who would
>rather have symbols that are easy to identify (and yes, even pretty) than to
>have three bits of information conveyed by symbol color.
I don't think that pretty has to be ignored to do this. I think that the
same concepts need to be integrated in a recognizable fashion. That means
that a simple Icon needs to be augmented with some additional information I
believe.
>In dos (at least as of the date I last used APRSdos), you cannot just click
on a
>symbol, and have a new window pop-up. The process of "hooking" an object means
>using the cursor to get there, awkward at best. On the other hand, in Mac and
>other windowing environments, this is a normal action. So, if I need to know
if
>station can accept a message, it is trivial to double click on the station and
>bring up a window, cntaining this (and tons of other information).
Yeah, but in a tactical situation with no time to spare, pattern matching
with your eye is a lot faster than clicking through 100 icons to find one
that can message. The dumb trackers make it even more important to have
this information plainly visible it seems to me.
>Furthermore, in javAPRS (and in findU for that matter), you never had the
>ability to send a message to a station anyway, so why should I be forced to
>place this information on my display???
It's about recognition of capabilities, not about convienence of the
programmer. How many Operating systems with windowing capabilities do you
know of that don't have UI design guides? This is what Bob is talking
about in my mind. But, you have to think about it at a high enough level
that your not burdened with the notion of the exact implementation that he
did.
>I never claimed you couldn't do it, or that any particular language made it
>difficult. Fact is, any programming language and windowing environment can do
>it. What I was claiming was that it wasn't done because it didn't make sense
to
>the developers of the programs, and further wasn't demanded by their users.
>There is a big difference here!
Yes, a handful of developers deciding the needs of 100,000 users, that's a
mighty big difference, especially given the opportunites for limited
knowledge and experience. Are you certain that every user of every non
APRSDos program knows every feature that APRSDos has, and that they
understand every feature of APRS as Bob perceives it? I think that they
don't, and therefore wouldn'31117/0912Z @:ZL2BAU.#73.NZL.OC #:9965 [Blenheim] $:2298-ZL3AI
R:031117/0851Z @:ZL3VML.#80.NZL.OC #:13008 [Chch-NZ] FBB7.00i $:2298-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : HUMOUR@WW
Rescue
------
The shipwrecked mariner had spent several years on a deserted island. Then
one morning he was thrilled to see a ship offshore and a smaller vessel
pulling out toward him.
When the boat grounded on the beach, the officer in charge handed the
marooned sailor a bundle of newspapers and told him, "With the captain's
compliments. He said to read through these and let us know if you still
want to be rescued."
Camping Survival Needs
----------------------
A Scout Master was teaching his boy scouts about survival in the desert.
"What are the three most important things you should bring with you in case
you get lost in the desert?" he asked. Several hands went up and many
important things were suggested such as food, matches, etc.
Then one little boy in the back eagerly raised his hand. "Yes Timmy, what
are the three most important things you would bring with you?" asked the
Scout Master.
Timmy replied, "A compass, a canteen of water and a deck of cards."
"Why's that Timmy?"
"Well," answered Timmy, "the compass is to find the right direction, the
water is to prevent dehydration..."
"And what about the deck of cards?" asked the Scout Master impatiently.
"Well, Sir, as soon as you start playing Solitaire, someone is bound to come
up behind you and say, "Put that red nine on top of that black ten!"
The Dangers Of Bread
--------------------
Just examine the statistics: Bread can be really dangerous!
More than 98% of convicted felons are bread eaters.
Fully HALF of all children who grow up in bread-consuming households score
below average on standardized tests.
More than 90% of violent crimes are committed within 24 hours of eating
bread.
Primitive tribal societies that have no bread exhibit a low occurrence of
cancer, Alzheimer's, Parkinson's disease and osteoporosis.
Bread is clearly addictive. Subjects deprived of bread and given only
water begged for bread after only two days.
Bread is often a gateway food item leading the user to harder items such
as peanut butter, jelly, butter, and even processed meat slices.
Bread is capable of producing dehydration. The human body is more than
90% water and bread can absorb water.
New born babies have been known to choke on bread.
Most American bread eaters find it extremely difficult to distinguish
between significant scientific facts and meaningless statistical babbling.
Read previous mail | Read next mail
| |
