this post was submitted on 08 Sep 2024
38 points (97.5% liked)
OpenStreetMap community
4010 readers
325 users here now
Everything #OpenStreetMap related is welcome: software releases, showing of your work, questions about how to tag something, as long as it has to do with OpenStreetMap or OpenStreetMap-related software.
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Join OpenStreetMap and start mapping: https://www.openstreetmap.org.
There are many communication channels about OSM, many organized around a certain country or region. Discover them on https://openstreetmap.community
https://mapcomplete.org is an easy-to-use website to view, edit and add points (such as shops, restaurants and others)
https://learnosm.org/en/ has a lot of information for beginners too.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's not deliberate. What is their motivation for doing that?
@NeatNit @openstreetmap
I would assume the same as the reason for warning about this in the first place? They don't seem to like devs tying things back to preset websites and think it deserves a massive warning icon.
There is no option for a tiny warning icon, all AFs get the same treatment - this might be a bad design, but there's no bad intentions behind it.
This isn't about what they like devs doing. It's about informing users about how the app works and what it does.
If they didn't want Organic Maps on F-Droid, they'd just kick them off. There have been plenty of opportunities for them to do it and seem justified, i.e. "we are removing Organic Maps from F-Droid forever because its devs are constantly complaining, causing us extra work and drama in long fruitless discussions". The opportunity to do that was explicit in the discussions and they didn't take it.
@NeatNit @openstreetmap
switching topics again are we?
They rolled out a massive new warning type and then didn't have all their apps accept it as OK. That is a deliberate choice. It is their ecosystem from top to bottom, they *chose* not to have the TetheredNet added to the list of allowed warnings in existing installs. If they hadn't wanted to make that choice they should have done the responsible thing and held the rollout until their app supported it.