<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=us-ascii'>
<style>BODY{font:10pt Tahoma, Verdana, sans-serif;}</style>
</head>
<body>
There's a similar option in the OpenTracker.<br><br>Scott<br>N1VG<br><blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;"><hr><b>From:</b> William McKeehan [mailto:mckeehan@mckeehan.homeip.net]<br><b>To:</b> bruninga@usna.edu, TAPR APRS Mailing List [mailto:aprssig@lists.tapr.org]<br><b>Sent:</b> Wed, 23 May 2007 13:09:40 -0700<br><b>Subject:</b> Re: [aprssig] Smart beaconing and the tragedy of the commons<br><br><!-- -->I would suggest that people using a reasonable "Min Turn Time" (specific to<br>the TinyTrack3 terminology i.e., the amount of time that must have past<br>between beacons before a turn will trigger a beacon) these problems could be<br>eliminated and still give a reasonable route.<br>-- <br>William McKeehan<br><br>On Wed, May 23, 2007 4:02 pm, Robert Bruninga wrote:<br>>> ...I for one am a little bit irritated that you<br>>> repeatedly blast SmartBeaconing while<br>>> having no experience with it.<br>><br>> I have plenty of experience with it. Most any day, most any<br>> time. All I have to do in my APRS is hit the SORT by LOAD<br>> button and see who is hitting out 99 beacons per hour (the max I<br>> capture), and it invariably is people running smart beaconing.<br>><br>> Yes, -those- users are very happy with smart-beaconing, since<br>> every single stop, start, turn and run is precisely documented<br>> as they run around town or commute. I am sure they are very<br>> pleased with smart beaconing. But it is at the expense of<br>> everyone else.<br>><br>> To me, NUMBER ONE in APRS is the network, and sharing it<br>> equitibly among all users and getting consistent results. In<br>> most areas, we simply cannot afford to have every corner pegged<br>> for every user! If people want nice tracks, then they should<br>> record their own GPS data and play it back on their own PC. Not<br>> try to do this on a single 1200 baud channel trying to be shared<br>> by 100 other users.<br>><br>> Again, I ask everyone to please step back, and read the "tragedy<br>> of the commons" (on the fix14439 page). Place the equitable<br>> sharing of the network formost in your mind and lets work<br>> together to come up with some smart beaconing settings that are<br>> equitable, under all conditions. (since the number one problem<br>> is set-and-forget human nature)...<br>><br>> If we can come up with a smart beaconing algorithm that is best<br>> for the network and fails-safe, then I am happy to support it.<br>><br>> Bob, WB4APR<br>><br>><br>> _______________________________________________<br>> aprssig mailing list<br>> <a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>> <a href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>><br><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br><a href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br><!-- --><style>
</style>
</blockquote></body></html>