HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
openstreetmap
operations
Maps & Geospatial2016–2023
openstreetmap / operations

operations

OSMF Operations Working Group issue tracking

8Distinct people
9Mentions
0Explicit recommenders
114GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

OSMF Operations Working Group issue tracking

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2016-09-28 10:36:59 UTC to 2023-06-20 13:17:44 UTC.

0123452016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC523
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110

What Hacker News says

9 sources
> That seems like a bunch of FUD. Do you think that the sites that do have ipv6 are spending any significant amount of time "dealing with stupid broken client configurations"? Ask Google, Cloudflare or Akamai engineers (those who actually deal with IPv6 problems) and they'll probably answer somewhere between "it's harder in practice" to "why can't peering issues go away when they f**king interconnect on IPv4"? It's not that IPv6 is inherently problematic, actually it's a lot better theoretically, but in practice unless you are a large network which has the capability to connect to everywhere in world and sidestep peering issues like Google, Akamai, and Cloudflare, you will encounter problems immediately. This is not theoretical, you haven't seen the likes of OpenStreetMaps who are experiencing peering problems (https://github.com/openstre
Read the rest
etmap/operations/issues/559), and not everyone can use US services which exposes them to risks like the CLOUD Act, which allows US law enforcement to access data anywhere as long as it is operated by US companies (most European companies for example). The real problem of deploying IPv6 is that despite record-high prices of IPv4 addresses and the cost of CGNAT (both monentary and performance-wise), it's still cheaper to do IPv4 only rather than dealing with the hassles of running both IPv4 and IPv6. With IPv4, you can just pick a Tier-1 carrier and you're guaranteed to traverse the whole internet, at least those who didn't proactively blocked you. With IPv6, you are exposed to ugly Tier-1 fights like when Hurricane-Electric tried to interconnect to Cogent to no avail (https://www.datacenterknowledge.com/archives/2009/10/22/peer...), even trying to bake a cake à la Microsoft-Mozilla browser cake wars (https://www.youtube.com/watch?v=7CObnXjmDtg), and even today it's still not resolved (https://www.theregister.com/2018/08/28/ipv6_peering_squabble...). Even Google is not spared with this interconnection woes: it's mitigated, sure, but there are still some parts of IPv6 internet that cannot reach Google, it's just those parts don't really use Google's services or have sane IPv4 interconnectivity (and to clarify, this isn't due to state-level blocking, those people just didn't realised that they don't have a path to Google via IPv6). Also some internet services (some video streaming protocols for example) also use other services than HTTP and will actually need to adapt to IPv6, but this is a very small issue (because you can fix software easier than pettyness) than the peering issue described above.
In Going IPv6 Only
The Operations Working Group, the sysadmins holding the servers together, are all volunteers. http://wiki.osmfoundation.org/wiki/Operations_Working_Group and keeps a list of hardware and open issues. https://github.com/openstreetmap/operations (more help always welcome). A frequent question is why the hardware bought and not rented hourly/yearly with a PaaS. First of all the bandwidth requirement are huge and it would put too much pressure on the organization to reach donation goals every year. Besides the donation runs you can also become a member (https://join.osmfoundation.org/normal-membership/) or you company a corporate member (http://wiki.osmfoundation.org/wiki/Corporate_Members). Unlike wikipedia the donation drive won't need months. If I remember correctly last year two companies gave 20.000 USD each. That said: donate now please
Read the rest
. disclaimer: work at https://geocoder.opencagedata.com/, we're a corporate member
In A Growing OpenStreetMap Needs Your Support

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.