-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding future redesigns #12
Comments
Respectfully, i agree with you Swagsy. |
Whilst I think there is no harm in change, it would have at least been nice to have a vote on this or something. There is a lot of people attached to the classic pleading emoji and considering this is no longer a corporate project, it would have been great to involve the community when making this change. Yes, there was an issue on the original repository but the change was then pushed without taking any community feedback. |
bad day for femboys (their beloved pleading emoji got removed) |
I'm joking a little while I say we lost an icon, but I genuinely preferred the older pleading face emoji and I'd love for it to stay around. |
I personally prefer the 2 new ones, they look cuter and hope to see more follow suite. This is a good change, not a bad one.
However, I do not think it is appropriate to lump all discord users behind that sentiment, as you are just one person and can not speak for everyone. |
That is not to mention it makes you look borderline embarrassing, to say the minimum. As for the emotes themselves: I can see why a poll or something of the type for those updates would be welcoming - considering this is still, somewhat, a community project. However, do keep in mind that the initial changes to those symbols were done in order to comply more in-line with the existing set that everyone is already familiar with, and to also fix some overall alignment issues as well. It was not an issue of "Don't Break what is not broken". People just make it look like as it was since they got used to the incorrect. |
Nobody I'm aware of in issues / PRs asked for a redesign of the I'm aware it is now more in line with A possible solution may be to redesign Would also love to see (per-emoji) polls in the future regarding changing existing emojis, as this is now a community project rather than a corporate one. |
Honestly the current one looks better, I don't think it needs to change in any way. |
It's been pretty much the standard for emoji implementations to move towards standardized representation, and that's the official position of the Unicode emoji sub-committee (Jennifer Daniel has some writings on this topic, but unfortunately I can't find the exact article I'm looking for atm.) The rationale is that this reduces potential for miscommunication, and that people expect their emojis to look a certain way. People don't think of 💃 as "dancing woman" (although the prescriptivist in me thinks they really should), they think of it as "a lady in a red dress making that specific pose". I fully agree with the less popular position that emojis should be varied and should be used to convey semantic meaning, rather than be used as pictographs, but there are also very real benefits to unifying how they look. And these benefits cannot be achieved unless everyone standardizes. I mentioned Jennifer Daniel earlier; in addition to being the chair of the emoji subcommittee, she was also the designer behind Google's iconic blob emojis. But even she changed her mind on this topic and has decided to go in the direction of standardization. Some examples of other emojis that follow this trend: Face with hand over mouth and face with spiral eyes. But a lot of other work indicates this general direction too--the filling out of the color space for colored hearts with light blue / pink / white hearts was partially motivated to even out those colors, and to bring different platforms closer together. The current effort to add "direction indicators" to emojis like trucks/cars etc. is also motivated by the same concept. My point is that this isn't an arbitrary "preference" thing, and that there is a lot of thought that went into these changes. Even though I disagree, this is the direction that Unicode has chosen. And it's not all bad, and besides, Discord has the convenient workaround of simply using custom emojis, which very few other platforms have. |
A request to make the face holding back tears emoji fit in more was opened in September of 2022, with somebody mentioning that the regular pleading emoji should also recieve an update in February of this year.
I'd argue the whole "poll" concept wouldn't work, similar to how nobody replied with any feedback regarding "please dont redesign this emoji" on the issue I mentioned above. People have a tendency to only check these things once something has happened, not in advance (and in the case that they do notice in advance, its much more likely for those that disagree with the change to tell their friends to vote no on it instead of it being a vote where the larger user group is affected). I have to agree with Ernests comment here that emoji designs should be more universal across suppliers and not arbitrarily made in order to look as unique or different as possible (leading to potential miscommunication). |
I don't know about you, but 22+ thumbs up in twitter/twemoji#563 seems like a pretty strong vote for a redesign to me. |
22 votes on a emoji-set used by 100M+ people daily is statistically negligible, especially considering those who have an issue with an emoji are significantly more likely to go and look for the issue then those who are happy with it. To note, this is also on the issue for the holding back tears emoji, while most people have an issue with the contextual change of the pleading face emoji. Wheres the emoji could previously correctly express "neediness" while also not distorting the original intention "pleading", it is now entirely incorrect in a "neediness" context I would agree with the change if previously this would create a misunderstanding (such as the "Face with hand over mouth" emoji that looked shocked on Apple devices, but laughing on others), but the previous emoji was unlikely to be confusing for the recipient regardless of platform and emoji set used by the original sender. |
You also should note that this repository is effectively maintained by 2 people, so your assumptions are not quite realistic. |
How is this remotely relevant to the discussion? If you can't have a sensible argument I'd prefer if you'd stay out of the discussion to prevent clutter. Enough projects are (primarily) maintained by a small set of people, but used by a wide audience, this is no argument to ignore community concerns or disallow discussion about changes. Saying that only 2 people maintain this repo significantly undercuts the hundreds of people who've done valuable contributions to the emoji pack as well... |
@smiba if you can't cope with other people sharing their opinions that don't align with yours, I suggest you don't engage in any discussion. I think I may have overlooked the fact that Discord already uses this fork of Twemoji. Anyway, imho I don't think you can please every single member of the community, there are always people who don't like an addition or change, but that's just how the world is. I also don't think @sofodesign will redesign every single emoji, if at all he will just fix small flaws, like with these 2 emojis now. If the original pull request hadn't gotten so many upvotes, this change wouldn't have happened in the first place. |
Yeah, but how many of the 100M+ people using it daily actually take part in the development of it? Not even 0.1%! |
Gonna toss my two cents in as far as the redesigns go: The holding back tears emoji was in fact pretty cursed. The redesign feels weird though, with the eye color being the main culprit as far as I can tell. Most emojis have brown eyes, so the black/navy blue looks really out of place. The pleading emoji change is causing the bottoms I know to have a series of existential crises. Eye color again looks to be the main culprit, since the black just looks out of place next to the brown of everything else. Eye direction is also somewhat of an issue, the upward glance of the old version looked especially pathetic, which was (best as I can tell anyway) part of the appeal. If all the emojis are being changed to black/blue that's okay, but as it currently stands the difference between the almost entirely brown features of the current set and the navy of the two new icons is off putting. My preferred solution would be to keep the brown, as that's one of the hallmarks of the set as a whole. I'm only one person though, so take whatever action you deem best. Also to those reading the thread, the 22 (now 25) thumbs up on #563 are specifically in relation to very cursed holding back tears emoji. |
I very much disagree with this issue and think both updated emojis are a big improvement. Changing just the "face holding back tears" emoji and not the "pleading face" emoji will make "pleading face" not only inconsistent with other implementations but also Twemoji itself. I understand your personal objection with this change but claiming to speak for the entire user base of Discord with a "vote" that never occurred and signing your message with "The People of Discord" is incredibly disingenuous. |
would love if the pleading emoji still looked upwards lol |
I feel like reverting the emoji's appearance for Discord's culture specifically feels like overreaching. They aren't the only platform using Twemoji. |
I don't think it's limited to discord's culture, but considering discord is a massive platform it will probably be the biggest group of users affected |
Maybe, but when I'm using Twemoji for a project, I want the emojis to look good. I don't want an emoji that looks bad because of its meme status. That's why I feel like it's overreaching. Sure, Discord may have the largest group of users involved, but it's still specific to a single entity. In that case, I think they should just fork it and readd the old emojis. |
i dont think the emoji should be reverted, if definitely looks better now, but a comprimise like @catgirl-doll proposed would be good |
I'd be happy with @catgirl-doll's proposal assuming the eye color was changed to brown, to match with the majority of the existing set. Also as far as response from Discord users goes:
For my own part, the eye color looks wrong, but otherwise the new versions are okay. |
@Irismono can you share a link to the threads you're mentioning? |
The emoji shown in the following tweet might align better with the other ones: https://twitter.com/luciascarlet/status/1641006053474140164?s=20 Edit: That's actually Twitter's new internal version of Twemoji. |
This seems like the worst of both worlds since the mouth makes it even more inconsistent with other platforms and the eyes do not placate those who want the old version back. |
Completely apart from the neediness/bottom aspect of the direction of the pupils: There were theories in some servers that the eye shape changed to look less like Precious Moments products. Was that a factor? |
i think this definitely looks better than the current design i think treating the two redesigns as a package deal is definitely a negative |
Sorry for taking your SVG file without permission, but I fixed some of the issues that I think your version has, such as the black pupils and the lack of eyebrows, and moving the face downwards. |
The svg doesn't contain any new assets, and was posted here to be used or adapted. No worries! That said: The pupil color is only debatably an issue, as brown and black eye colors are inconstent between released Twemoji; both in jdecked's fork and the official Twitter published pack. The lack of eyebrows and the face being tilted upwards are intended to be evocative of the old design, as they convey a similar emotion while being more in line with the present art style than the defunct 14.0 Just like the currently used |
The eyebrows being present is a subtle downgrade as far as I'm concerned. They move the expression more towards hopefulness or confusion than begging. I'd personally argue that the eye color is better brown. If I had graphic design skills beyond MS Paint scribbling I'd offer to go through and update the existing set to be more uniform. My observation has been that the discrepancies are on less commonly used emoji, which is likely why they haven't been addressed. |
I’d suggest to specify a ZWJ sequence for the legacy design, but then – they’re really very similar. |
What's the big deal. Surely the intelligent solution is to create a folder called: "legacy emojis" and put the old ones in there. Then everyone wins. No need to erase emojis from history 🙄 |
I don't think anyones concern is history related, just the change itself. Restoring it might still be the best choice, but @bsoap-cat 's edit is pretty good too, although I'd probably leave out the eyebrows. Still doesn't work as well as the previous one, but if this is the compromise that can work I'm ok with that :)
You'd have to ask the Unicode Consortium |
ZWJ sequences are not required to be RGIed by Unicode. |
Of course, but it would be even further out of line for twemoji to just introduce their own new sequences, not knowing if they suddenly will be in use in the future. Using a free sequence without reservation from the Consortium is foolish |
We must obey the Consortium. Long live the Consortium. O7 🖖 |
thx, but the version without eyebrows was made by @catgirl-doll. I added eyebrows because I thought it looked good. |
regarding redesigns of emojis in rev dbb2a10, I found that they're not twemoji-colr friendly. |
Dear developer,
after thorough discussions and future-oriented predictions, in favor of platforms such as Discord, the user base has voted on keeping the already-existing, standard yello face emojis as they are and not become a subject to change, as seen with the recently 2 updated ones. We respect the 2 recent changes, but with all due appreciation, we would not like to see more alternations of the classic twemojis in future releases. We thank you in advance.
~"Dont't break what isn't broken"
Much Love,
The People Of Discord
The text was updated successfully, but these errors were encountered: