<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Knowing what software/firmware/hardware
a remote station is using can allow an APRS client software packet
or APRS user to exploit features specific to the other end's
platform.<br>
<br>
If I'm considering plopping down a chunk of change for a D710, I
can identify D710 users to contact to get their opinion of their
radio.<br>
<br>
For instance, if I see a Yaesu APRS radio (FTM-350 or VX-8 and
suspected FTM-400), and I'm running a non-AX.25 -SSID, I know that
I shouldn't attempt an APRS messaging QSO because they don't
support it.<br>
<br>
If I see APRSISCE/32 at the other end, I know I can send an
Item-As-Message packet to them to communicate a location,
regardless of whether it's RF, -IS, or any combination between me
and them.<br>
<br>
If I see a station that's beaconing fast and furious and know that
it's APRSdroid, I can suggest that they upgrade to the latest
version that fixes a old bug in the SmartBeaconing code that can
cause that problem.<br>
<br>
I could go on and on with manufactured examples, but the bottom
line is that if information is available, a use will be found. If
information is hidden, then no one will ever be able to use it for
anything.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
On 10/24/2013 10:52 AM, John Wiseman wrote:<br>
</div>
<blockquote cite="mid:76E3EC7CC0984794BC1A67276EA4D284@Lenovo"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style>.hmmessage P {
PADDING-BOTTOM: 0px; PADDING-TOP: 0px; PADDING-LEFT: 0px; MARGIN: 0px; PADDING-RIGHT: 0px
}
BODY.hmmessage {
FONT-SIZE: 12pt; FONT-FAMILY: Calibri
}
</style>
<meta name="GENERATOR" content="MSHTML 10.00.9200.16721">
<div><span class="041324514-24102013"><font size="2"
color="#0000ff" face="Arial">Ok, I must be missing something
fundamental here. Why do we (as software authors) care what
system generated a packet? Shouldn't we just be concerned
with the content?.</font></span></div>
<div><span class="041324514-24102013"></span> </div>
<div><span class="041324514-24102013"><font size="2"
color="#0000ff" face="Arial">I can see that if a particular
package is generating something that is outside the spec and
is causing problems, it may be necessary to identify the
source so the author can be contacted, but in general what
do I (or my users) gain by knowing whether a packet was
generated by my software or anyone else's?</font></span></div>
<div><span class="041324514-24102013"></span> </div>
<div><span class="041324514-24102013"><font size="2"
color="#0000ff" face="Arial">73, John G8BPQ</font> </span></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>