Administered by:
@notjustbikes@notjustbikes.comOh, good. Unicode 16.0 has added a "face with bags under eyes" emoji. I'm going to be using that one a lot.
I'm still kinda mad they refused to allow the addition of a "no cars" emoji though.
They said they don't want to have anymore individual "no" emojis, but they also won't remove the ones they already have.
So we have 
but have to do 
and hope the platforms display it properly some day.
@notjustbikes Perfect reply for when someone says "b-but all disabled people need cars!!!1!one!"
@rubenerd @notjustbikes and I’m highly amused that this emoji appeared as a ? In a box 
@notjustbikes Unicode consortium in the 90s and 00s:
well, we can add the letter "A" three times for Latin, Greek and Cyrillic, but will unify the idiographs into single codespaces for Chinese, Japanese and Korean, even in cases when there are important differences between how they are written in each language.
Unicode consortium in the '20s: you get no "no cars" emoji, but here's a face with bags under the eyes.
@notjustbikes I've seen "no cars" symbols in the wild. They're often on wide paths through parks. I've yet to see a "no bikes" sign in the wild.
@soviut they are very common in the Netherlands, usually outside of shops when they don't want people to parks their bikes out front.
@notjustbikes Can't really remove characters from unicode. What else should fill that spot? Old text is just gonna break and show the wrong symbol
@stefanheinz yes, I know that. I never suggested they could or should?
@notjustbikes "they also won't remove the ones they have"?
@notjustbikes right i see now, that bit of the sentence is still meant to be from their perspective. I read it as being a response to the first part
@notjustbikes I can kind of understand them not wanting to add a new code point for it, in the same way they're not adding new code points for accented latin alphabet characters: the existing ones are there to ease conversion with legacy character sets, but outside of that set you need to rely on combining diacritics.
They seem to be doing the same with emoji, defining new ones as combinations of existing code points. I imagine a proposal to do the same with would be more effective than adding a new code point.
@notjustbikes Do you know if the reason for the rejection was documented somewhere? The Emoji committee only publishes very little information about declined proposals (only the name, date, and status. No reason).
It makes sense that they don't want to add a new codepoint for NO CARS. The question would be if they would be open to having it as a recommended ZWJ sequence (basically recommending platforms to display + ZWJ + as a separate symbol). As of Unicode 16.0 it's not on that list.
@notjustbikes Proposals for Unicode 17 are currently open until 2025-07-31. However, declined proposals can't be resubmitted within four years. While the post you linked is from 2019 according to the official list NO CARS was only submitted in 2022 (Or maybe that was already the second attempt? The wait period used to be two years).
@notjustbikes Mastodon allows custom emojis, so while it's a work around, not as broad a solution as you'd like, you could add the custom "no cars" emoji to your instance and it will be seen where ever your post lands.
At least one facet of your life will have it :-)
@craige@social.mcwhirter.io @notjustbikes@social.notjustbikes.com My instance doesn't yet have the no cars sign, but we do have :cybertruck-fire: so I guess that's something
@notjustbikes One nice thing about Mastodon - instances can add emojis themselves. Perhaps we can push the Fediverse to include +
@notjustbikes the Unicode Consortium won't remove any previously-approved characters because they want anything that could historically be written in Unicode to forever be valid. If you change or retire a character, any existing text would also change.
This is also why the Kanji ghost characters won't be removed: https://en.wikipedia.org/wiki/Ghost_characters
@Diameter8140 yes, I know. And it makes sense that they can't remove characters.
But it's still annoying that we have and 
but not no cars.
@notjustbikes @Diameter8140 is it not possible to use + Unicode combination character + in that order?
@juandesant I've never been able to get it to work but maybe some platforms support it?
, but it could be a problem for other things)@notjustbikes @juandesant It's probably not supported on any (major) platform, because it's not on the list of recommended Emoji ZWJ Sequences: https://www.unicode.org/emoji/charts/emoji-zwj-sequences.html
Maybe 
️ does it's job?
As it should be. No cars is the default condition unless specifically noted!