<p></p>
<h3 dir="auto">Problem</h3>
<p dir="auto">OpenStreetMap has a custom <a href="https://wiki.openstreetmap.org/wiki/Shortlink" rel="nofollow">Shortlink</a> algorithm that is used to generate a URL link to a specific point on the map in a terse format. That algorithm being custom means no other mapping tool (that I've seen documented) uses it as a shortening method. Being custom means the development team needs to keep updated the algorithm code, and documentation for it. If it were switched to a known standard algorithm, it would allow more interoperability with other tools, and would allow pruning out that code from the website (allowing the website code to just focus on OSM-specific business logic).</p>
<h3 dir="auto">Description</h3>
<p dir="auto">Replace the "Short Link" UI logic to use a known standard algorithm. The current Shortlink algorithm is similar to <a href="https://plus.codes" rel="nofollow">Plus Codes</a>, and the Plus Codes system has been adopted by many other mapping and addressing systems, so replacing it with that algorithm via a Plus Codes library would allow simplification of what the OSM site needs to do to calculate/parse "Short Links" and make generating OSM "Short Links" from other applications easier (as many will already have a Plus Codes library pulled in). Though I note there has been some reluctance to add Plus Codes to other areas of the application (search bar: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="310542210" data-permission-text="Title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/1807" data-hovercard-type="issue" data-hovercard-url="/openstreetmap/openstreetmap-website/issues/1807/hovercard" href="https://github.com/openstreetmap/openstreetmap-website/issues/1807">#1807</a>); if that system is not preferred, the Geohash, and Geohash-36 systems are also similar to the current Shortlink algorithm and could be considered as more possible alternatives.</p>
<h3 dir="auto">Screenshots</h3>
<p dir="auto"><em>No response</em></p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/4205">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLPWOWW643QQNRIDSLTXXGJNJANCNFSM6AAAAAA37K36WA">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLN25JGXBGEGOLAPQ5DXXGJNJA5CNFSM6AAAAAA37K36WCWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHG6VTK3E.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/issues/4205</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/4205",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/4205",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>