Matija Nalis

see also https://github.com/commons-app/apps-android-commons/issues/5689, https://github.com/commons-app/apps-android-commons/issues/5131#issuecomment-1368408843

Other approaches I see: - slide from the left - e.g. Osmand (which has menu icon on lower left) and OpenStop, K-9, Libretorrent, Nextcloud, AntennaPo, NewPipe, Fedilab (which have menu...

> Using SC to remove the tag when a name is changed still seems like a good idea to me. Agreed! When SC users answers a name quest, `fixme=name` (and...

> Alternatively, you could also just show the form blank, i.e. ignore pre-existing names. > And I really don't know if it is worth it to implement for the rather...

> Also, why not check if `fixme` value contains `name` if really so many variations should be checked? I don't like hardcoded lists, especially of "free form values". That's a...

> Looking at taginfo, the only thing that really seems worthwhile to check for (it is even documented, not bad) is fixme=name. The rest are just crumbs There is a...

> Draft PR to follow when I got all tests working Any luck @kmpoppe ?

I'm on the edge about including that option in StreetComplete. On the one hand, it has some use and seems deterministic; but on the other hand, it might confuse users...

mention @torhovland @westis @RubenKelevra @CloCkWeRX @cperrier @jonpsp @rhhsm @mcliquid - who seem to have had interest in `mtb:scale` quest for StreetComplete previously; perhaps they'd like to help with shorter descriptions...

I too am worried about _"💤 Not an overwhelming percentage of quests have the same answer (No spam)"_. When you @knkski say _"These crossings are common around me in the...