and then there are all kind of things to handle like aliases
3 curtidas
Ah-ha!
I’d missed that repo, thanks @j.jaffeux we’re now back in business 
Apple, with a fallback to unicode 
5 curtidas
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
5 curtidas
test 
test
must be something in your theme?
3 curtidas
- twitter uses the same strategy
- slack uses the same strategy
- discord uses the same strategy
Maybe there’s a reason?
7 curtidas
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 
1 curtida
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.
Yes you are right, we should make them converge, no big harm though.