<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Badges]]></title><description><![CDATA[<p dir="auto">Big fan of the product and progress.</p>
<p dir="auto">Lots of badge ideas and requests:</p>
<p dir="auto">Add multipliers of five or 10 to badges. For example, storm trooper times 5 10,20 or 50. This can be done for international traveler, higher moorings, anchor etc.</p>
<p dir="auto">For winds experienced: Gale 1 &amp; 2, tropical storm, Hurricane 1,2,etc?<br />
10,000, 20,000 leagues etc or some other way to express lots of miles traveled.<br />
50, 100, 200, 300, 400,500 nights on the hook, mooring, dock.<br />
Number of US states visited. A badge for every 3-5 states? Badges could be the shape of each state?<br />
Number of countries visited. A badge for every 3-5?</p>
<p dir="auto">Badge for user submitted features that are used.</p>
<p dir="auto">Add a badge if you could determine if a boat had transited a lock. </p>
<p dir="auto">Continents visited badge. You get one at your second continent, etc. </p>
<p dir="auto">Following up on the continent, visiting each major ocean or sea</p>
<p dir="auto">Beta Badge: for those people who used Saillogger as it developed. (I know we were freeloaders) these people were your data point guinea pigs.</p>
<p dir="auto">Paid supporters. Call it whatever you want. Voyager badge, Bouy badge (keeping you afloat?) something…</p>
<p dir="auto">I’m sure you could get community support to design the badges to get that off your plate.</p>
<p dir="auto">Thank you again for the great product.</p>
<p dir="auto">Andy</p>
]]></description><link>https://community.saillogger.com/topic/60/badges</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Jul 2026 10:35:24 GMT</lastBuildDate><atom:link href="https://community.saillogger.com/topic/60.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 19 Jun 2024 14:27:47 GMT</pubDate><ttl>60</ttl></channel></rss>