<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ysleepy</author><text>Maybe messages should include a coarse timestamp to prevent replay of old messages by some adversary.&lt;p&gt;Someone could resend a month old &amp;quot;yes&amp;quot; with your valid signature to a question someone asks now.&lt;p&gt;Also it might be beneficial to include sequence numbers or message IDs and for example echo the last 4 ids in following messages so recipients can detect holes. - The chat could insert some placeholder to notify recipients of missing previous messages.</text><parent_chain></parent_chain></comment><story><title>Show HN: A new protocol for packet radio including ECDSA and compression</title><url>https://github.com/brannondorsey/chattervox</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>vvanders</author><text>Does this do any sort of FEC? One of the things that makes stuff like this tricky(and APRS in general) is that one flipped bit throws off the whole decode.&lt;p&gt;From what I&amp;#x27;ve seen out there would be a 40% improvement[1] in just base APRS if there was some form of basic FEC built into the protocol. Sadly most of &amp;quot;state of the art&amp;quot; is stuck back in the 80s.&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;eludium.stensat.org&amp;#x2F;mcguire&amp;#x2F;projects&amp;#x2F;FX-25&amp;#x2F;FX-25_performance.htm&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;eludium.stensat.org&amp;#x2F;mcguire&amp;#x2F;projects&amp;#x2F;FX-25&amp;#x2F;FX-25_perf...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Show HN: A new protocol for packet radio including ECDSA and compression</title><url>https://github.com/brannondorsey/chattervox</url></story>