https://weeklyosm.eu/archives/17480
29/08/2024-04/09/2024 Tricks and tips on how to draw buildings [1] | © Koreller | Map data © OpenStreetMap contributors Mapping [1] Koreller showed us a series of tricks and tips on drawing buildin…
@NeatNit @gedaliyah @openstreetmap
F-Droid do provide more detail about why they warn that something has an anti-feature, but only make that easily accessible if you run their code natively on your device. If you're on the web interface you have to figure out which of the links in the external links section isn't actually external and look in there.
Their excuse for this is that their website can't parse their own file format that they invented for themselves.
@NeatNit @gedaliyah @openstreetmap
Oh, and they also deliberately buried the rollout of the new anti-feature in the middle of an obscure blog post rather than doing the responsible thing and prompting users to make a decision about it.
https://f-droid.org/2024/04/04/twif.html
@organicmaps is probably on borrowed time before it is also hidden from search.
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.