Started writing it
https://codeberg.org/silverpill/feps/src/branch/main/9098/fep-9098.md
Listed requirements for the Emoji object.
I should probably describe the microsynax there as well, and how custom emojis are rendered.
Started writing it
https://codeberg.org/silverpill/feps/src/branch/main/9098/fep-9098.md
Listed requirements for the Emoji object.
I should probably describe the microsynax there as well, and how custom emojis are rendered.
Requirements in that section are meant for those who want maximum compatibility. For example, JPEGs and images larger than 256 KB are supported by Pleroma and others, but Mastodon doesn't allow them.
Non-square emojis are a bit more complicated. They are not rejected by most servers, but might not be displayed properly by clients.
I just visited your instance and made a screenshot of how emoji is rendered by web UI (attached). The emoji is present, but I can't tell what is depicted there. Some clients enlarge custom emojis on hover, but not Mastodon, so I have to open the image in a new browser tab, or zoom in the page. This is no ideal, hence the recommendation in the FEP.
@silverpill @julian @hongminhee you have listed "Image is a square" but is definitely not true for Misskey. And Mastodon renders Misskeys long emojos just fine.
Actually mastodon does fine with long emojos now too :fep_400e:
@liaizon @julian @hongminhee I added a text explaining this additional requirement: https://codeberg.org/silverpill/feps/src/branch/main/9098/fep-9098.md#additional-requirements
Best practices for rendering custom emojis will go into different section (WIP).
@silverpill @julian @hongminhee ugh mastodon android squishes this. These are both Mastodon bugs as far as I am concerned. I think as long as you specify what you are making maximum compatibility with that seems OK but long emojos are INCREDIBLY popular on all the misskey and misskey adjacent fediverse areas. So I would argue that usage should be spelled out in the FEP as well.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.