Emojis update

[j.jaffeux (Joffrey Jaffeux)]

discourse-emojis/dist/emoji/unicode at main · discourse/discourse-emojis

and then there are all kind of things to handle like aliases

[Richie (Richie Rich)]

Ah-ha!

I’d missed that repo, thanks @j.jaffeux we’re now back in business

Apple, with a fallback to unicode

[mk0r]

@j.jaffeux

• different platforms support new released emojis at different speed, so you could have user A on platform 1, creating a post using an emoji available on this platform, which will then be seen by user B on platform 2 which doesn’t support yet the latest emojis released few weeks ago => tofu box (in the world of fonts, “tofu” is a blank rectangular box that appears when a character cannot be displayed).
• custom emojis. Discourse supports custom emojis which are not mapped to a character and are just images.

This seems strange way of doing things. Rendering emoji as images in the flow of text feels against the grain. The vast majority of users will be very used to their device/OS native emoji so looking at some less-good or different version will feel strange.

The vast majority of websites use user-native emoji, how is this ever really a problem? shouldn’t the default be the user’s native emoji, with the option to do custom emoji sets as a plugin or user customizable option?

Current approach feels and looks inelegant

[Richie (Richie Rich)]

Is anyone else seeing massive emojis appear in posts?

[j.jaffeux (Joffrey Jaffeux)]

test test

---

must be something in your theme?

[j.jaffeux (Joffrey Jaffeux)]

@mk0r

The vast majority of websites use user-native emoji, how is this ever really a problem?

• twitter uses the same strategy
• slack uses the same strategy
• discord uses the same strategy

Maybe there’s a reason?

[Richie (Richie Rich)]

@j.jaffeux

must be something in your theme?

No, sorry, I’d missed a screen shot to show it was an upload by the looks of things.

If I edit the post this is what I see:

Strange eh

[Divinebaboon]

Question: For the Unicode set, it is the ones in the “Sample” column right? If so, these are the same exact ones as Noto, are they not? I’m just a bit confused as to why both are offered if they are the same set.

[j.jaffeux (Joffrey Jaffeux)]

Yes you are right, we should make them converge, no big harm though.

[MichaIng]

I just stumbled over this, as our forum default (also when resetting the option back to its default, is “Twitter” while it says “deprecated to Twemoji”.

It makes sense that “Twitter” emojis are deprecated, since the name “Twitter” is deprecated (and the new platform turned into an abused shit hole mostly) . But also it probably makes sense to not change things without admin consent.

About this default: is it the default the own Discourse instance was originally shipped with, or are these global to all instances, and hence can change? Do new instances have Twemoji emojis enabled by default?

[Canapin (Coin-coin le Canapin)]

@MichaIng

Do new instances have Twemoji emojis enabled by default?

If this is still the case, it might change in the future, see:

Emojis, would it be prudent for Discourse to Fork Twemoji?

Moving this to feature @lindsey , at some point we may have to rethink our default emoji set We do not want to be stuck on a set that has stopped evolving Every year Apple champion a few new emojis to great fanfare it is a shame to be perceived as a product that is behind here What other open options are out there? Is there a non fork one that looks great and would be a great default?

[MichaIng]

@Canapin

If this is still the case, it might change in the future, see:

You mean if it is not yet the case?

My point is:

• It looks weird that “Twitter” emojis are explicitly stated deprecated in the list, while they are still the default, i.e. the “reset” button in our case still applies these deprecated Twitter emojis.
• So I was wondering whether the default has really not changed in upstream code, along with renaming “Twitter” to “Twitter (deprecated to Twemoji)”, or default settings changes do not apply retrospectively to existing Discourse instances. In this particular case I see an argument to not change the default on an existing instance, so admins can always revert to what their forum was shipped with, and settings they never touched do not change without them explicitly changing them.
• Other wording: Do the “reset” buttons apply the Discourse defaults (which may change), or do they apply whichever value the Discourse instance was originally shipped with?

Well, I guess the default has really not been changed yet, the other theory seems quite complicated behavior .

[Moin]

Twitter is still the default, even on new installs

config/site_settings.yml

I think “reset” always resets to the default of the current version. For example, Normalize emails was enabled by default about a year ago DEV: Enable the normalize_emails site setting by default by Drenmi · Pull Request #29952 · discourse/discourse · GitHub, so reset changes the setting to enabled now.