[aprssig] Maximum APRS Packet Lengths and 3rd party use?

[Jim Alles]

Generally, point taken. I wasn't specific enough. My apologies for the
blanket statement.

This part, I still believe is correct:

​
As far as server-side (filter) subscriptions, there are none *required* for
an IGate, + "to operate".

which I think answers Scott's second question.

Generally, I think it is a good idea to get to know the in's and outs of
the specific software one is using - tread carefully. Read the
documentation. Test your assumptions. You might even find a bug once in a
while.

As far as that goes, I am still waiting for a response from the author(s).

Peace,

Jim A.

On Wed, Nov 30, 2016 at 6:33 PM, Lynn W. Deffenbaugh (Mr) <
ldeffenb at homeside.to> wrote:

> On 11/30/2016 6:06 PM, Jim Alles wrote:
>
> ​
>
> ​​
> As far as server-side (filter) subscriptions, there are none required for
> an IGate, and it is strongly recommended to start out with that field
> blank, in your IGate client.
>
> What might go in there is a very limited list of 'buddies' who might get
> VIP treatment for some reason. Or very specific weather alerts. But you
> need to learn a lot about that before swamping the RF side of things.
>
> ​​
>
> This is not a valid general statement.  APRSISCE/32 supports a filtered
> APRS-IS feed for local display without gating anything but messages
> addressed to recently heard local stations from the -IS feed to the local
> RF environment.  Before making statements like blank filters for IGate
> clients, it would help to know to which APRS software is in use.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161130/90c8a4b7/attachment.html>