[aprssig] !x!

[Lynn W. Deffenbaugh (Mr)]

Thanks for the link.  Since APRSISCE/32 doesn't "archive" then I'm 
thinking it doesn't apply to me.  Or is it supposed to be "don't archive 
or display"?

An interesting conundrum is whether or not the archival sites are 
expected to remember the !x! from a beacon and suppress recording 
messages as well, or if it must appear in each and every packet?  And if 
you're expected to remember it, doesn't that mean that you're archiving 
some information about station that has requested to not be archived?  
Gotta love/hate ambiguities.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 12/30/2011 11:10 AM, Steve Dimse wrote:
> On Dec 30, 2011, at 10:50 AM, Lynn W. Deffenbaugh (Mr) wrote:
>
>> Is this behavior documented somewhere?  Google really doesn't like searching for !x!
> It is in the aprs spec 1.1 addendum
>
> http://www.aprs.org/aprs11.html
>
> though this only shows the shortened form !x!. x-no-archive is an internet standard flag and the original opt-out and is also accepted by findU (actually the test string is x-no-ar, so it can be shortened if desired).
>> And is it honored by other APRS-IS viewing implementations?
> A quick check of LB9KE-7 shows aprs.fi ignores it and APRSWorld respects it (the latter has a posit from Dec 6 that did not include !x!). That aprs.fi never got called on it shows just how few people care.
>
> Steve K4HG
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>