Follow

We will be spending the rest of this week improving federation support and fixing bugs.

Thank you for your support, pixelfed wouldn't be what it is today without this amazing community.

❤️

@pixelfed thank you! It works pretty great already! Please fix the bug that prevents me from setting a profile picture on iOS. Thanks!

@pixelfed
I made a comment to test federated emojis:

pixelfed.social/p/PixelFed/123

Will the fix be reflected there, or will it work only on newer posts?

@They call me Rick 😎 Generally, shortcodes are not consistent between software/apps. In my opinion, shortcodes should not even be used at all outside of chat software/apps (like Slack, Messenger, Telegram, etc.). These were never meant to be used in forums, comments, and websites.

If you check the #Unicode #Emoji list, not every single approved emoji have a shortcode suggestion. This introduces a major inconsistency as far as shortcode-based emoji input is concerned.

What developers need to do is to actually and literally implement Unicode Emoji -- direct input, not using shortcodes. Direct input will work across all software and apps.

Using your example, :bobcat: I don't find any corresponding emoji for it in any fediverse platforms I tried. If PixelFed implements the shortcode :bobcat: then it only shows in PixelFed but shows as a shortcode everywhere else. Then you'll get used to this shortcode and demand that other platforms implement it too. Yes, it already happened years ago because people were used to shortcodes in one particular mobile platform or app and it's not working in another (say Android or Slack).

However! If PixelFed implements the actual Unicode Emoji itself (and not by using shortcodes), then it will show everywhere else, regardless of platform, software, apps. (Do note, you still need font support -- which can be easily solved by a "website" by using @-font-face CSS rule).

Shortcodes are not bad. But it is very limited. As I've mentioned earlier, not every Unicode Emoji have a shortcode suggestion. There are inconsistencies in multi-word emoji shortcodes too. Is it bobcat, bob-cat, bob_cat, catbob, cat_bob, or cat-bob? The Unicode Consortium did not implement a rule about this.

What is a :bobcat: emoji? How does it look? Believe it or not, there is no "bobcat" in the Unicode Emoji list, at least none that I can find. If so, then it means it is a custom emoji that no one else have except those who implement it manually.

Does it look like a :cat: or a :smiley_cat: or a :pouting_cat: ? If so, then use the Unicode suggested shortcode, which is cat, smiley_cat, or pouting_cat. At least that way, there is some consistency as those shortcodes came from the Unicode Consortium. But again, very limited, as not every Unicode Emoji have a shortcode suggestion. Some even have very long ones like human_female_darkskin_curlyhair_redhair or something.

Implement Unicode Emojis as Unicode Emojis and not shortcode emojis. That's the proper way of doing things, less JavaScript too. If it doesn't show properly, then either you don't have a font, the website itself doesn't use @-font-face to add their custom emoji font support or your browser has a bug in its font-fallback mechanism but the developers of your browser keeps on insisting "it is working as intended" (*cough*Chromium*cough*).

Here are some __direct input__ emojis (not using shortcodes).
🐱😹😼😿

Developers can add their custom shortcode emojis and custom emojis altogether (Apple does the latter a lot), their call. But users must not demand their favourite shortcode and custom emoji be implemented everywhere. And face it, it won't show up anywhere else. I see this a lot from Mastodon users. Their names have funny shortcodes in it, which is ugly, really. Personally, I'd rather see boxes (some fonts and browsers do this) or none at all (some fonts and browsers do this), instead of a strong list of shortcodes that makes everything unreadable. Do not forget, we are a fediverse. We need to start thinking "does this emoji show up correctly elsewhere?" I use emojis in my name, but it's all direct input, no shortcodes. I let your OS and software interpret it instead of displaying a bunch of shortcodes in my name that your OS and software can not interpret.

@yahananxie custom emojis are a Mastodon feature that has become part of our culture now. They're not designed to be interoprable with the rest of the internet, but they work among other servers of the fediverse. I think we all know they're not a standard, but here's the thing:

We don't care.

We like them and we want them to work in our servers. If your implementation doesn't support them, we'll adopt one that does.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!