[Xastir-dev] a readable version of the latest official APRS spec?

[Alan Crosswell]

Thanks Tom and Tapio.

I believe I also made dupe checking in my aprsdigi code always be turned 
on so it's already suppressing dupes to RELAY and WIDE.  I guess I just 
assumed dupe checking is a good thing and didn't think it made sense for 
the *user* of the digipeater to be the one to decide whether dupe 
checking is to be done or not.  So, I think my code already implements 
everything that's needed and I'll be leaving my RELAY and WIDE aliases 
in until things settle down.  We still have old-style non-fancy TNC 
digis in this area anyway!

73
/a

Tapio Sokura wrote:
> Tom Russo wrote:
> 
>> In a nutshell, as I understand it:
> 
> 
> And in another nutshell, a digipeater that has working dupe checking no 
> matter what path the user uses shouldn't need much _code_ changes. Maybe 
> implement hop count limiting/trapping some way if it's not implemented 
> already.
> 
> What I'm trying to say is that there should be no need to completely 
> remove features like the traditional RELAY and WIDE digipeating from the 
> code, just keep them as configurable items. There are many places in the 
> world that are not jumping through Bob's new n-n paradigm hoops anytime 
> soon so it would be nice to be able to use current software versions for 
> more "traditional" paths.
> 
> Someone mentioned digipeating longer/shorter paths and packets from 
> close/far away depending on channel loading, it sounds like something 
> that could be nice in a digipeater. But this isn't really part of the 
> new n-n agenda, just a feature suggestion if you feel like you'd like to 
> implement something new in the digipeater..
> 
>   Tapio
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev at xastir.org
> https://lists.xastir.org/mailman/listinfo/xastir-dev
>