Order Tray | Contact Us | Home | SIG Lists

[aprssig] NOSaprs update - cross port digi with callsign substitution

William McKeehan mckeehan at mckeehan.homeip.net
Wed Jun 22 19:29:52 UTC 2005


Help me understand. I have taken a couple of snips from your earlier message.
In these snips you point to the user knowing what needs to be done with
his/her packet as opposed to the digi sysop. I have not been involved with
APRS as long as some other have, and as such I can not think of examples where
the no source routing approach would cause problems. Can you give some example
situations where some "flexibility" would be needed.

Not poking, just looking to better understand.

On Wed, June 22, 2005 3:05 pm, Robert Bruninga said:
> But that approach is based on one thing:
> *having the network KNOW what you want
>   done with the packet*
> There are many sysops who are quite happy to
> define where your packets should go, and will
> happily make a network do it.  But that kind of
> approach on an ad-hoc come-as-you-are
> kind of system that APRS is supposed to fullfil
> is full of pitfalls and kills the kind of flexibility
> that APRS was intended to provide, and that is
> to use it for what you need at the time.
> Ah, but Do what?  Many people have very different needs
> for their APRS packets, and very different ideas about
> how they want their packets to be used.  Trying to force
> ham radio operators into a one idea, one-app system has
> the potential to kill the system.  HAM interests
> are too varried to try to take those draconian steps.
William McKeehan
Internet: mckeehan at mckeehan.homeip.net

More information about the aprssig mailing list