<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div id="ydpca8ffc97yahoo_quoted_2430571366" class="ydpca8ffc97yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div dir="ltr" data-setdir="false">The issue that you have described has nothing to do with the protocol and everything to do with how different licensed manufacturers implemented it and the level of acceptance testing that went into it before it was approved for release. However, I am a pragmatist. It is the present APRS-trademarked ecosystem and if one wishes to play in it, one must be sensitive to its nuances beacause wholesale replacement is unlikely given the turmoil associated with something as simple as getting people to agree to moving to a frequency a couple decades ago. :-)<br>
</div><div><br></div><div>On Thursday, August 17, 2023 at 10:42:45 PM EDT, Charles Gallo <charlie@thegallos.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpca8ffc97yiv8175309041"><div>While this is true for the data, I think that the whole datagram for things like how to digipeat (which Bob was always having to teach folk the Widex-y etc) might really be the broken part, when you look at things like LoRa. The big difference is that today, we have so much computing power relative to 1982 (just look at the computing power in even a RPi Pico, at $4) that the parts where we are worrying about KPC 3s and other TNCs and their limited brains is what holds us back. It is like saying you have to write everything to be compatible with an 8088 PC running DOS3.3<div>Will we be telling a bunch of folks “nope, you can’t play with that hardware”? Yep. But having the compute power to keep a database in memory, and do a lot more calculations would eliminate a whole bunch of problems, and probably sole a lot of the issues with the difference between Wides, Fill In, iGates etc<br clear="none"><div><br clear="none"><div dir="ltr">-- <div>73 de KG2V</div><div>Charlie</div></div><div dir="ltr"><div id="ydpca8ffc97yiv8175309041yqtfd03260" class="ydpca8ffc97yiv8175309041yqt9089111823"><br clear="none"><blockquote type="cite">On Aug 17, 2023, at 9:52 PM, Ev Tupis via aprssig <aprssig@lists.tapr.org> wrote:<br clear="none"><br clear="none"></blockquote></div></div><div id="ydpca8ffc97yiv8175309041yqtfd02613" class="ydpca8ffc97yiv8175309041yqt9089111823"><blockquote type="cite"><div dir="ltr"><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class="ydpca8ffc97yiv8175309041yahoo-style-wrap"><div dir="ltr">Back in the day, the protocol working group realized the importance of assuring that the protocol would be sustainable into the future.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">To that end, open the protocol document and look up "User Defined Data Format". By abiding by it, you can encapsulate all sorts of new stuff into an existing datagram and by doing so, you assure nothing is broken when being transported through IGates or the APRS-IS.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">It is a huge win, and a real testimony to the working group's future vision (waaaay back in 2004). Bravo to them!<br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Ev, W2EV</div><div dir="ltr"><br clear="none"></div></div><span>_______________________________________________</span><br clear="none"><span>aprssig mailing list</span><br clear="none"><span>aprssig@lists.tapr.org</span><br clear="none"><span>http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</span><br clear="none"></div></blockquote></div></div></div></div></div></div>
</div>
</div></div></body></html>