Over the past few days, my perspective on OpenStreetMap (OSM) has undergone a seismic shift. For the longest time, I held OSM in the highest regard, viewing it as a beacon of transparency and people-centricity amidst a sea of profit-driven tech conglomerates.
Chapter 1: The Banner of Surprises
My view started to waver a couple of days ago when a new donation request banner popped up on the main OSM page. Though its sheer size and prominence were unsettling, the real issue lay in the near-invisible close button. When I voiced concerns on its ready-for-production state, opposition awaited me on the other end. Was this a shift in OSM’s priorities?
Chapter 2: The Amazon Alliance
Another revelation added fuel to the fire. Scrutinizing OSM’s 2022 and 2023 budgets, I stumbled upon a yearly expenditure of €24,000 directed to Amazon for S3 storage. This alliance with the tech giant seemed out of character for OSM. With an impressive arsenal of OSM-owned servers, the choice to rely on Amazon’s rented storage raised questions about OSM’s commitment to independence.
Chapter 3: Speaking My Mind
Emotions ran high as I took to the forums to articulate my frustrations. Admittedly, my initial approach was less than tactful, potentially causing offense. I since rephrased my statements, but my core concerns remained:
- OSM’s puzzling choice to rely on Amazon’s AWS.
- The opaque nature of information regarding S3 use within OSM.
- The seemingly wasteful storage of files on the expensive S3.
These revelations painted a rather concerning picture of OSM’s current trajectory.
I intentionally choose not to delve deeply into the now-publicized details concerning S3 dependence here. For a comprehensive understanding, I’d recommend referring to the original thread. Rehashing all the specifics here would be redundant.
Chapter 4: Lost in Dialogue
As conversations unfolded, a pattern began to emerge. Some comments seemed baseless, and when challenged, many simply turned a blind eye [1] [2] [3] [4]. This behavior wasn’t exclusive to the Amazon issue. It seemed to be a growing trend [1], even among those holding significant roles within OSM. A constructive dialogue relies on evidence-based arguments, and I found this lack of engagement disheartening.
Chapter 5: The Silenced Voices
My frustrations were further amplified when certain posts were taken out of context, resulting in the closure of the entire discussion thread. While I acknowledged my initial lack of professionalism, I took steps to rectify it. The decision to close the thread felt like a suppression of open dialogue, an ethos I believed OSM staunchly upheld.
Chapter 6: Reflection and Realization
These series of events forced me to confront a bitter truth: OSM’s priorities seem to have shifted. While my concerns about transparency were met with indifference, minor transgressions in tone drew significant attention. My principles are unwavering: I can only support an OSM that champions transparency, values its community, and remains open to feedback.
Endnote: Parting Ways, but Not in Spirit
My journey with the global OSM, in its current state, must sadly come to a halt. Yet, this doesn’t signify the end of my commitment to the open-source community. I will continue to support local OSM projects, like the OpenAEDMap, and will ensure that my AI-related projects [1] [2] remain accessible to all. While my vision of revolutionizing OSM mapping might be on hold, my passion for open source and my dream of a transparent, user-centric digital world remain undeterred.
Photo by Alvesgaspar. See terms.