This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
Even so, wouldn't you rather have one set of bugs and security issues, or at most one per platform, than as many as there are apps (or worse, as many as there are app/platform combinations)?
In that case, the bugs would be in the social media apps/websites, not in the operating system's text rendering routines. That's a much better place for them to be. Websites are very restricted in what they can do, and on mobile platforms so are applications.
It also would never have gotten anywhere near this situation to begin with. In the olden days, forums displayed emoticons by doing replacements on strings like
:)or:smile:. There's really not that much that can go wrong with a system like that. (Often enough these codes still work in fact, but they are now replaced with Unicode rather than an image.)Unicode emojis have two big problems. The first and biggest is the design, they were made to be composable, as the designers foresaw that it would be extended and apparently considered that a good thing. For example, [woman] + [sunglasses] gets you a woman wearing sunglasses. I remember the reaction when the 'pregnant man' emoji came out, but really, what else should [pregnant] + [male modifier] do? That's not crazy, it isn't even trying.
You can have a cutesy couple, [man] + [heart] + [woman]. Or you can have a cutesy gay couple, one of whom is pregnant, and both are wearing sunglasses, [man] + [sunglasses] + [heart] + [pregnant] + [male modifier] + [sunglasses]. They could each additionally have a hairstyle, hair color and skin color defined. At this point it's becoming a design flaw that they didn't include the equivalent of parentheses to formally specify the order of composition (though let's not give them ideas). And we want to put this all in the operating system's text rendering routines. Define them all in fonts! As ligatures! Madness, I tell you.
The only limit is that unofficial combinations don't need to be supported (though you are certainly welcome to try), as long as you can display the component parts in order. For example, an old enough system is going to render [pregnant] + [male modifier] as a pregnant woman and an Ares symbol.
Which brings me to the second problem, the Unicode Consortium. There's a single body that decides this, and it can be lobbied, and is it ever. Everybody wants their pet issue represented, and they've really got no reason to deny anyone, because the design already allows it. In the olden days this wasn't a thing. You try convincing phpBB to add your thing, and MSN, and AOL, and whatever else there used to be.
This is why I liked this decision, because it means sanity won at least once. Consider the alternative, that you could say "cutesy gay couple, one of whom is pregnant, one is black with curly hair and one is white with short red hair, with a bald Asian boy and a white girl with long, straight dark hair". This kind of composition is already allowed, but could've been made mandatory to support, in the dark mirror universe.
More options
Context Copy link
More options
Context Copy link