OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 07:31l 297 Lines 13187 Bytes #999 (0) @ WW
BID : 810-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 28, 3/6
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030201/0945Z @:ZL3VML.#80.NZL.OC #:58557 [Chch-NZ] FBB7.00i $:810-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Tue, 28 Jan 2003 09:07:42 -0600
X-Message-Number: 13

hehe      There is plenty of leadership here.  I think the problem started
by using the programmers as the deciding influence on what should be in the
Spec's.  Sorry if this sounds like I'm bashing the programmers here. They
have done a great job with there Apps and I mean them no disrespect. How
ever there is a conflict of interest ($$) when you have those working on
separate pieces of software all deciding on what the specs should be.  Sure
there opinion should be taken into account but to leave it in there hands
alone is asking for problem.  I realize this sounds harsh but the conflict
in interest really takes its toll in this case.

    If a programmer is creating his own app of his original purpose.
i.e... (Bob and APRS)   Then sure they should be the main influence on the
Specs.   In most cases the Specs are written before the Program is.  Simple
because the programmer need guidelines to know what his program is to do.
In the case of APRS all of Bobs notes should have been used in creating the
Specs.  Any new feature created sense should be added as needed.
Programmers then should work towards fulfilling the Specs in there app's.
Sure the programs would very greatly do to the programmers talents.   But
in the end you would have the required consistence between programs to make
this system work.

    I think most of the APRS community look towards Bob as its leader. I
have seen him receptive to new ideas as well as having a clear
understanding of the fundamental capabilities of APRS.(Just stating the
obvious)  He is very active in the workings of APRS still.  I don't see
that in all of the programmers working on APRS apps. This maybe do to flame
wars that happen from time to time.  I know of one programmer that does not
participate on this list for that specific reason.  Its a shame because
he's a very competent programmer who also has a clear idea of APRS.

    All of these concepts that Bob has of the capabilities should be added
to the Specs.  Along with any new ideas that have been implemented sense.
It is up to the programmers to add to or ignor these features.  The Specs
should be the full capabilities of APRS.  This will set a goal for
programmers to shoot for.  Sure some will fall short but it is by far easer
to inclued a smaller portion of the feature within a more complete version
of the same feature then the reverse.

Pat

----------------------------------------------------------------------

Subject: Re: regarding RACES
From: "Bob D." <n2iph@comcast.net>
Date: Tue, 28 Jan 2003 10:14:26 -0500
X-Message-Number: 14

I think what most are missing here is it is not entirely an issue of
interference or eavesdropping on military communications but the purpose of
shutting down amateur communications (if deemed necessary) is to also
reduce the noise level (unnecessary communications) and
uncontrolled/potentially unfriendly communications. There are a number of
other reasons, but here's a few of my thoughts.

When/If all unauthorized communications are suspended, then you are left
with only those authorized comms (RACES, MARS,
Government/Military) -and- the rest is  potentially enemy
communications. Its easier to tell who the bad guys are. During this
time, RACES stations can only handle communications as authorized by the
government agency they serve with other RACES stations (plus a very few
exceptions like the Military & FEMA).

Look at Desert Storm/Desert Shield, when most all the Saudi Hams had
their gear confiscated by Iraq, sadam did not do this to prevent them
from getting their DXCC, he wanted to eliminate the possibility of these
operators and their equipment being used against him. One or two of them
were able to stay on the air and provided information to the US and the
Coalition that was helpful (see back issues of QST from the period).

What about during W.W.II, and clandestine radio operators here in the
US?
What about all those pirate (never ID) stations you here on the bands
(Amateur or otherwise), think they are just out there having fun using
the ether for chatting w/o a license? They could be (and some are)
communications between terrorists/spies/drug cartels/etc. Just because
you listen and don't here them talking (in plain language) about blowing
up a building or coordinating the next attack on a US Navy destroyer
doesn't mean they are not communicating (in coded phrases) something
subversive.

Since most of our APRS network is not on a frequency authorized for
RACES operations during emergencies, yes it would have to move (and the
license holders of those stations would have to be part of RACES to
continue operating) or shut down. And, I might add, you can't wait until
it happens to decide you want to be a member of RACES just so your DIGI
(or whatever) can stay on the air to help, you need to be (should be)
part of RACES _now_ (at least in my County, where I make the rules).

Bob, N2IPH
Radio Officer
Cumberland County NJ RACES

----------------------------------------------------------------------

Subject: RE: Incident Command Post Symbol
From: "Bob D." <n2iph@comcast.net>
Date: Tue, 28 Jan 2003 10:22:09 -0500
X-Message-Number: 15

testing of software features, there's a good idea :-)

----------------------------------------------------------------------

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 10:57:17 -0500 (EST)
X-Message-Number: 16

On Tue, 28 Jan 2003, Juergen Frank wrote:

>>The following table describes the colors used in APRSdos to convey the "type"
>>of station that a given SYMBOL is representing:
>>
>>*  WHITE:..... A Full-up APRS station that is message capable
>>*  GRAY:...... A Tracker or other station without message capability
>>*  CYAN:...... A moving station with CSE/SPEED or a Dead Reckoned Station
>>*  BLUE:...... The previous position of a MOVED station or object
>>*  YELLOW:.... Your own active OBJECTS you are transmitting to the net
>>*  VIOLET:.... Objects placed on the map by others
>>*  Dark GRAY:. Old Symbols not updated in the last 80 minutes or more
>>*  BLACK:..... Old Symbols that have been "killed" by the originator
>>*  RED:....... Emergency, Alarmed, or otherwise unknown symbols
>>
>>NOTE: Nothing requires anyone to use COLOR like I did in APRSdos to convey
>>this information, but no matter how it is presented, it is important
>>information about a SYMBOL on an APRS map that should be conveyed somehow
>>graphically to the user..
>
>Why can't a station be 'message capable' and 'moving' (with
>CSE/speed/(height))? It should be white and cyan at the same time...

Its not perfect.  It was the best I could do..

>So the idea of indicating something at the stations symbol is good, color is
>the wrong way to do it IMHO.

That's why anyone is welcome to come  up with a better way!

>What about having small 'icons' directly attached to a station/object's
>symbol (small envelope for message capable, small crossed envelope for not
>capable, moving station has a moving indicator right now (shorter or longer
>line in driving direction) and old symbols will be greyed out also (UI-View
>at least), missing is an indicator foor own or foreign objects...)?

Yes, all good ideas!  Go for it...

All I want is for the information to be presented in an obvious way, I
dont care how...

Bob

----------------------------------------------------------------------

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 10:59:30 -0500 (EST)
X-Message-Number: 17

On Tue, 28 Jan 2003, Juergen Frank wrote:

>I strongly have to disagree to your statement about APRS in Europe!

Ah, this is good news.

>How do you come to the opinion that it's used as a DX system here?

From the frequent posts I see here on the sig.  I can only go by what
people tell us, and the last thread I saw on this issue about how APRS
was used in Europe told us it was mostly used for DX and not public
service, etc...

>I encourage everyone I see, sending long pathes in his/her packets, to
>shorten them to make the network run better.

>Crazy path-definitions like WIDE7-7,TRACE7-7... Can be seen anywhere in the
>world, mostly sent by unexperienced users!

Yes, that is the problem..

Bob

----------------------------------------------------------------------

Subject: Re: regarding RACES
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Tue, 28 Jan 2003 11:04:29 -0500
X-Message-Number: 18

Err, maybe you meant Saddam took the ham stations away from the Kuwait
hams.

I believe that the 504th PIR out of North Italy arrived in time to stop his
advance into Saudi Arabia.

73 de Ronnie

----------------------------------------------------------------------

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Steve Dimse <k4hg@tapr.org>
Date: Tue, 28 Jan 2003 11:24:56 -0500
X-Message-Number: 19

On 1/28/03 at 9:21 AM bruninga@usna.edu (Bob Bruninga) sent:

>Yes, and if I walked out, we would have a tower of Babble now...
>The term "locked" is a figurative term as you well substantiate in your
>paragraph above.  I stand by my statement.  Though I will eliminate
>any reference to the type of latch mechanism on the door to the room:

That is a pretty significant change, you accused people of false
imprisonment, a felony. Please try not to publicly accuse me of any other
imagined crimes. In this instance, I was taking a course of action I felt
was best for APRS. I believe the other people present were being honorable
and doing the same, and it is unfair of you to misrepresent our actions or
motives.

>>>"Either I agreed to do the spec with all its shortcomings and without
>>>what I considered to be some of the fundamentals of APRS (how
>>>information is displayed) or the other authors would go their own way
>>>and do it anyway they individually wanted."
>
>That was the threat posed to me in that room.

I really don't want to rehash what brought us to that point, but in brief
my motiviation was that I was tired of you making unilateral changes in the
APRS spec, and trying to dictate the way things were to happen, and who
should be allowed to write a program using the APRS protocol.

Had we not formed the APRS WG, APRS would not be where it is today. Yes, we
wrested some control of APRS out of your hands, but there is more than one
way to do things, and I was tired of it being Bob's way or no way.

>And the total inability of that APRS-Working Group (as a group) to agree
>to absolutely anything since and make one single formal change to the SPEC
>or to document the APRS-IS since, is a testament to the validity of that
>last sentence.

Generally Bob, problems like this start at the leadership. If the APRS WG
has done nothing, maybe you should look to yourself. No doubt the Sprouls'
distance from APRS has not helped, but there are two new members, and if
Keith and Mark choose not to participate, then maybe they should be
replaced, along with everyone else that is not going to be involved.

The alternative explanation to a lack of leadership is that no one else
thinks of these proposed changes as being important. Understand, this is in
large part what we were aiming to stop, the willy-nilly alteration of APRS
to suit your latest whim...

>...
>I think there is lots of progress and great movement in APRS.  But I will
>continue to fight to see that APRS adheres to a few fundamental
>objectives.  I use these concepts to see if new ideas are "good" for APRS
>or are "bad" for APRS:
>...

I can agree to all of them except:

> 4) All users regardless of who's applications software in that
>  same area will "see" the same information displayed as intended
>  by the originator of that information..  (Again, I am not saying
>  'how', just 'what' should be displayed)...

This is simply not possible...in fact your own beloved altnets are
specifically designed to prevent this from happening. The success of APRS
means that displaying information has become like drinking from a firehose.
There are many different philosophies for user interface, many different
ideas that can and should be tried. It is up to the programmer to invent
and implement them, and for the users to choose which suits their needs. It
should not be up to you, or anyone else, to dictate how data is to be
displayed on-screen.

Imagine if the original RFC for email had sopecified how email should be
displayed onscreen to provide a common experience for the user. Sure, you
could use any program to check you email without a learning curve, but
unless the person writing the spec was incredibly psychic, there could have
been no multi-windowed email programs, web mail, or html mail. Specs should
specify the interchange of data, and the programmer should be free to offer
his own UI.

Steve K4HG

----------------------------------------------------------------------

[commercial content deleted]

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 14:51:51lGo back Go up