@rory I know you're joking. But the consumers don't all have full unicode available.
Parsing and analyzing OSM database is a PIAS already. Lets not make it worse by inserting emoji, flags and other un-semantic content or tags.
It will certainly save you from having to keep adding letters to that wretched acronym.
I have a natural aversion to acronyms so I usually use a formula of the type “gender-based” + noun (e.g., gender-based discrimination), which I believe should remain understandable for generations to come. In a previous life I often had to dig into 200-300 year old documents and, after penetrating the handwriting and the language, you were still left to deal with the expressions of the day. Not fun 😛
Of course, 🏳️🌈 works too. It will *not* stand the test of time but it does have the advantage of being language-neutral (today, it is just as understandable to an English speaker as it is to a Korean speaker).
With just over 150 tagged objects, I don't think it's too late to propose for a change. 😁
@GOwin I've added those ~150. I'm reviewing everything tagged with "gay" and adding it.
@rory OSM / VGI is about making it easy to contribute. Using non-standard chars seems to be the opposite ;)
Saves the work of having to document them. 😜
@rory I looked at the discussion. It was a flashback to twenty years ago when the exact same discussions were being had concerning this “#Unicode” thing versus #ISO-8559 or even whatever #DOS used at the time. 🙂
With the hindsight of that experience I would say: ignore the naysayers. They were wrong.
Pictograms (#emoji) are here to stay, they are useful, and software should be fixed, sooner always better than latter. Someone has to break the chicken and egg circle for things to move forward.
@61 playing with computer systems, finding the edge cases, seeing where they break. It's the hacker spirit!