Skip to content
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

Revert pleading emoji or accept/create a more representative redesign #32

Open
Cassumbra opened this issue Apr 7, 2023 · 7 comments
Open

Comments

@Cassumbra
Copy link

The current redesign diverges way too far from the previous version and expresses an entirely different intent. It also shares much too similarity with the current "face holding back tears" design.
I am making this as a separate issue from #12 because I feel as though that issue does not carry the same intent as this one. Apologies if they are too similar.
To clarify:
I see this issue as: "Please change or redesign the pleading emoji"
Whereas #12 seems to be: "Pleading emoji is fine, but don't make any more changes"

Perhaps I am simply misreading the text though. Sorry if so.

@Woofer21
Copy link

Woofer21 commented Apr 7, 2023

I disagree here, the new pleading emoji design brings it inline with all other platforms designs of the emoji, which is important to have when someone on one platform could see the emoji as something and someone on a different platform could see it totally differently.

You can see here how the old one does not fit in at all with any of the others.

@TomasTokaMrazek
Copy link

I personally dislike the new pleading emoji quite a lot, as it conveys completely different meaning. But I have to agree with @Woofer21.

Your best bet is to add it as custom server emoji.

@barkloaf
Copy link

barkloaf commented Apr 7, 2023

there is nothing wrong with the original pleading face design. I'm not saying anything about the sentiment expressed in #12 but what I will say is that I think that the old pleading face should be brought back as soon as possible without the prospect of redesigning it (hence #27). it's not really that different from the other vendors (variation among vendors is to be expected!) and I am struggling to think how it could be misinterpreted. furthermore, due to the cultural impact that the old pleading face had (which is even mentioned on the emojipedia page!), I think it's pretty likely that even if the emoji is ambiguous (which, once again, I believe it not to be), people will have been exposed to it enough to know which emoji it's supposed to be. the original twemoji pleading face is very quintessentially a pleading face; I think it's the other vendors that aren't making sense.

as for the notion of "adding it as a custom server emoji" that @TomasTokaMrazek mentioned.. I assume you're referring to discord? if so, discord requires you to pay for the usage of other servers' emojis when you're not in that server. this is not a solution; why would I want to give my money to discord? furthermore, more platforms than just discord use twemoji; this isn't really about discord at all. any time I have the opportunity to set which emoji set an application uses, I choose twemoji. I even have it as the only emoji set installed on my arch system so that all emojis are forced to be twemoji. I am under the belief that twemoji is the only good emoji set. I believe it should be the definitive design for emojis and that's why I care so much about bringing back a great design.

@barkloaf
Copy link

barkloaf commented Apr 8, 2023

While you do have to pay for Discord Nitro to use custom emojis on other servers, you can just send an image of the pleading emoji or any other kind of custom emoji shrunken down to a smaller size.

I think I made it pretty clear in my message that this literally isn't about discord. what do you do on a platform that you can't upload images to? what do you do on platforms that have explicit formatting for images (for example, not being able to place them in-between characters like you can with emoji)? what about when someone else sends the emoji without the image? I highly advise you re-read what I wrote. emoji exists for a reason and are not substituted by pictures (which was ultimately why #26 was closed).

@TomasTokaMrazek
Copy link

While you do have to pay for Discord Nitro to use custom emojis on other servers, you can just send an image of the pleading emoji or any other kind of custom emoji shrunken down to a smaller size.

I think I made it pretty clear in my message that this literally isn't about discord. what do you do on a platform that you can't upload images to? what do you do on platforms that have explicit formatting for images (for example, not being able to place them in-between characters like you can with emoji)? what about when someone else sends the emoji without the image? I highly advise you re-read what I wrote. emoji exists for a reason and are not substituted by pictures (which was ultimately why #26 was closed).

It's not about Discord per se, but to be brutally honest, the majority do not care for your projects or your personal emote preference. The fact is, that Discord has 150 milion MAU. In a world of open source its quite normal, that the OSS project is closely related to its biggest user and the user in turn makes contributions to the project. For example pfSense makes a lot of contributions to FreeBSD. From the storm that occured after the pleading emoji change, it's apparent, that Discord should contribute to this project or take over by employing the designer and coder behind twemoji.

There is one clear future of this project. If the development gets disassociated from Discord userbase (as we already see in the recent change of pleading emoji), Discord will eventually make its own emote set (by forking twemoji for example) in order to stop alienating its community. And if Discord stops using this project, it will simply die as it will be very niche emote set for very small userbase. Eventually other projects will rather use Discord emote set, if open source of course. I have seen this scenario a few times already.

@barkloaf
Copy link

barkloaf commented Apr 8, 2023

If the development gets disassociated from Discord userbase (as we already see in the recent change of pleading emoji), Discord will eventually make its own emote set (by forking twemoji for example) in order to stop alienating its community. And if Discord stops using this project, it will simply die as it will be very niche emote set for very small userbase. Eventually other projects will rather use Discord emote set, if open source of course. I have seen this scenario a few times already.

yeah, that's understandable. apologies if I was a little harsh previously, I was under the impression that people were trying to make it seem like the pleading face emoji design was only associated with communities on discord (it was also very cherished on twitter who afaik is still using the original repo).

it's apparent, that Discord should contribute to this project or take over by employing the designer and coder behind twemoji.

I'm not entirely clear on the situation. twitter is in complete shambles right now for obvious reasons, the CDN that provided the original twemoji seems to have shut down, and I don't think any strides will be made at twitter to implement unicode 15. I know that the maintainer of this fork was a twitter employee, but I'm not sure if they worked on twemoji previously (either way, maintaining this is a selfless job; massively appreciated!).

@12Me21
Copy link

12Me21 commented May 6, 2023

This article has some relevant information about the popularity of this emoji: (particularly on twitter)
https://blog.emojipedia.org/a-new-king-pleading-face/


I'd suggest moving the pupils upwards, since that feels like an important feature of the original. (I'd really like to move them further, but I think at that point it differs too much from the other platforms' designs)

svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 36 36">
	<defs>
		<clipPath id="eyes">
			<circle r="6" cx="11" cy="15"/>
			<circle r="6" cx="25" cy="15"/>
		</clipPath>
		<g id="pupil">
			<circle r="5" fill="currentColor"/>
			<ellipse rx="2.082" ry="2.675" transform="translate(-1.636,-0.636) rotate(45)" fill="#FFF"/>
			<ellipse rx="0.914" ry="1.175" transform="translate(2.5,2) rotate(45)" fill="#FFF"/>
		</g>
		<path id="mouth" d="M 3,0 s -3,-1.5 -6,0" stroke-width="2" stroke-linecap="round" fill="none" stroke="currentColor"/>
		<path id="eyebrow" d="M -2,1 s 2,0  4,-2" stroke-width="2" stroke-linecap="round" fill="none" stroke="currentColor"/>
	</defs>
	<!-- head -->
	<circle r="18" cx="18" cy="18" fill="#FFCC4D"/>
	<!-- mouth -->
	<use href="#mouth" x="18" y="26" color="#664500"/>
	<!-- eyes -->
	<circle r="6" cx="11" cy="15" fill="#F5F8FA"/>
	<circle r="6" cx="25" cy="15" fill="#F5F8FA"/>
	<!-- pupils -->
	<g clip-path="url(#eyes)">
		<use href="#pupil" x="11.5" y="14" color="#664500"/>
		<use href="#pupil" x="24.5" y="14" color="#664500"/>
	</g>
	<!-- eyebrows -->
	<use href="#eyebrow" transform="translate(10 7)" color="#664500"/>
	<use href="#eyebrow" transform="translate(26 7) scale(-1 1)" color="#664500"/>
</svg>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants