Hey all, WhyEssEff here

Over the past two-and-a-half or so years of being the sort-of-official emoji czar, the emote repository has grown to contain approximately 2300 distinct pictographs. As has been remarked over my tenure, this has unfortunately come with a lot of disarray. In order to address this, let me break it down in order to give proper context for it all.


The Problem

Hexbear’s emote shortcodes are notoriously obtuse and lack enforced standardization. A patchwork fix was applied to solve this in the refork, being keywords, but these only work when you are searching through the emote picker, not when you are using :shortcode-notation:.

The primary reasoning behind why this problem is a conundrum to fix is what I will call ‘shortcode rot.’ Essentially, what this entails is that:

  1. an unintuitive emote shortcode, for one reason or another, makes it into the emote repository.
  2. enough time passes for said emote to be used across multiple posts and comments.
  3. the shortcode now cannot be altered without breaking these posts’ and comments’ use of said emote.

The sources of unintuitive/unstandardized shortcodes, as far as I understand it, tend to fall into these categories:

  • attempts at brevity (e.g. :biderman:)
  • emote is older than my tenure (e.g. )
  • emotions and natural language representation of pictures are ambiguous (e.g. linguistics)
  • syntactical ambiguity and non-standardization (e.g. one way this is used advantageously is that this is how we have three representations of 1984 in our emote base, :nineteeneightyfour:)
  • WhyEssEff trying to be clever (e.g. :)
  • the other ones that I can’t think of.

The Proposals

To preface, these are merely the options I am considering at the moment. Furthermore, the subsequent poll is merely me gauging feedback on these potential options. I reserve the right not to enact or fully enact whatever the majority opinion falls behind, because I a) have a life and may not be able to address the issue meticulously, b) can’t please everyone with whatever shortcode schema we do end up with, and c) kind of am attached to certain wrinkles in the repository and would ultimately be operating on my own discretion no matter what as the head and sole maintainer of the repository.

With that out of the way:

PROPOSAL 1: Discretionary Rename Effort

Plan of Action: As I sort through the emote database, I change the ones that stick out as unstandardized and/or ambiguous by my own discretion, updating them as I go and making a pinned masterpost that I update when I change a shortcode so people can stay informed about new shortcodes.

Pros:

  1. The one that is the most realistic for me.
  2. Solves the problem for the most erroneous ones.

Cons:

  1. My discretion is biased and fallible.
  2. Changes to shortcodes that may break some older content.

PROPOSAL 2: Strict Standardization and Total Overhaul

Plan of Action: All emotes are strictly standardized according to an enforced style guide, on top of the previous proposal.

Pros:

  1. Most accessible.

Cons:

  1. 99% chance I’m not going to do this because it sucks to implement.
  2. Really really breaking changes to shortcodes.
  3. Ehhhhhhhhhhhh

PROPOSAL 3: Do Nothing

Plan of Action: It is what it is

Pros:

  1. No broken shortcodes, archive preserved.
  2. I can just keep to a standard in the future.
  3. I don’t have to do anything.

Cons:

  1. The problem remains unsolved, so all the aforementioned issues.

The Poll

So, in order to collect feedback, here’s what I ask:

Respond with the emote that corresponds to the proposal in a top level comment, except for the last option, which I’ll explain below.

  • (:dean-smile:) for Proposal 1: Discretionary Rename Effort.
  • (:dean-malice:) for Proposal 2: Strict Standardization and Total Overhaul.
  • (:dean-frown:) for Proposal 3: Do Nothing.
  • (:dean-neutral:) for something else, and explain what you suggest in your comment.

If you want to vote for a proposal that is suggested by someone else using

Again, non-binding poll, I’m just trying to gauge the temperature on this. In about a week, I’ll check this post again and tally it all up, and then I’ll take that and decide how to move forward. Thanks all

32 points
*

IIRC the shortcodes are the key column of the emote. If you change them, then all previous uses in posts/comments will not load the emote. If you want to rename any, let me know and we can write a regex to go through and replace any instances in the database.

edit: also, its maybe possible we can enhance the inline emoji window to use keywords as well. would have to do some experimentation with it.

permalink
report
reply
23 points

will keep this in mind, interesting option since keys are locked on frontend

permalink
report
parent
reply
17 points

I forgot, also we won’t be able to update federated posts in other instances, so those will get forever broken.

permalink
report
parent
reply

I haven’t explored other instances at all, but if updates sync is there an easy way to trigger the “there was an update to this post” push or whatever Lemmy uses to synchronize them?

permalink
report
parent
reply
11 points
*

Since the federation update, when I pick an emoji with the picker I get markdown to a URL that doesn’t contain the shortcode.

For example inserts:

![dean-neutral](https://www.hexbear.net/pictrs/image/48c31f9a-8487-48f0-afce-9db1db5fb5d6.png "emoji dean-neutral") 

Notice that the url to the png: https://www.hexbear.net/pictrs/image/48c31f9a-8487-48f0-afce-9db1db5fb5d6.png doesn’t contain the shortcode.

So right now the database has posts mixed between what I’ll call the “old format” :shortcode: and the “new format” with the URL. The new format shows up in other instances and the old format doesn’t.

Shouldn’t it be possible to run a migration in the database, and switch the old format with the new for all posts? Then disable this on-the-fly shortcode substitution that the frontend is doing.

From then on we will have to use the picker, but the emoji can change name without braking old posts. And eventually the frontend conversion can be added to the backend to restore the old behaviour.

This would simultaneously solve the issue where emojis don’t show up in other instances some times.

permalink
report
parent
reply
8 points

Yeah we added extra code in our hexbear frontend to add handling for the ‘old format’ codes. We did sorta have plans to update all the old usages to the new one, but we just never got around to it during the big migration.

permalink
report
parent
reply
9 points

Now you have two problems.

permalink
report
parent
reply
6 points

I’m glad someone has already said this because this is what I was going to suggest as well. It wouldn’t be that hard to crawl with a simple python script.

permalink
report
parent
reply
25 points
*

(Note: this is not in any way an official statement by the admin team, I’m just a tech dweeb)

Proposal: Do Nothing, but improve searchability by making the shortcode autocomplete also search by tags, not just the canonical name.

We have the ability to add basically unlimited alt-names or descriptors to the tags for each emote, which has made searching in the emoji picker much more viable even for obscure emotes (provided they are well-tagged). Problem is, nobody uses the emoji picker, most people don’t even know it exists.

Make sure the library is reasonably well tagged and make that tweak to the searching and this whole conundrum goes away.

Examples below of some existing tags from a previous effort to tag all the emotes:

We might also want to make the alt-text more descriptive for people with screen readers but that’s a separate conversation

Edit: Oh it looks like a dev (comrade makotech222) has already chimed in on this below:

also, its maybe possible we can enhance the inline emoji window to use keywords as well. would have to do some experimentation with it.

This would also basically address the following other suggestions:

https://hexbear.net/comment/4396592

https://hexbear.net/comment/4397267

https://hexbear.net/comment/4396837

https://hexbear.net/comment/4396793

https://hexbear.net/comment/4396237

https://hexbear.net/comment/4395861

https://hexbear.net/comment/4397894

https://hexbear.net/comment/4395895

https://hexbear.net/comment/4397730

https://hexbear.net/comment/4397711

 

secondary option if this isn’t feasible: remove the unicode emojis from the emoji picker so it goes straight to our custom emotes when opened, and make it more prominent in the UI somehow (highlight it in a different color, make it bigger, make it sparkle, idc). And still finish the job tagging them all

permalink
report
reply
12 points

This! This is the one

permalink
report
parent
reply

please! I’m sick of having to tell people the emoji picker exists every time this comes up

permalink
report
parent
reply
2 points

honestly my problem with the emoji picker is that it’s often super slow. ofc as soon as i look at the picker it’s actually pretty fine so maybe I just need to try using it again

permalink
report
parent
reply

Do this!

permalink
report
parent
reply

I kind of like how obtuse it is. It’s part of the culture.

permalink
report
reply
9 points

finding a new one is like finding a new easter egg in a video game

permalink
report
parent
reply
23 points

Add duplicates of badly named ones with new standardized names. And filter out the old ones from the emote picker so they don’t get used much again.

permalink
report
reply

I second this one

permalink
report
parent
reply

the emote repository has grown to contain approximately 2300 distinct pictographs


permalink
report
reply
12 points
*

For reference there are 3,782 emojis specified by Unicode (counting every kind of combination like skin tone or gender modifiers).

We’re catching up.

permalink
report
parent
reply

emoji

!emoji@hexbear.net

Create post

A workshop for the memes of production.

Submit new emoji here.

A good submission is:

  1. Visually clear at a small size (120 pixel width) [This does not mean upload the small image, this means upload the source image or full size cutout but test prior.]
  2. Have a transparent background to the greatest degree possible. This online tool can remove many backgrounds.
  3. Display a clear emotion or purpose
  4. If including text, should be properly sized to be readable
  5. “Evergreen” and not something that will be irrelevant after the next news cycle
  6. Formatted in PNG, GIF, or SVG to make our file optimization cycles easier. If svg initially, send svg in a seperately hosted link to WhyEssEff. Same with gif, as we render them as mp4 IIRC.
  7. Have proposed title as the title of the post, nothing more, nothing less.
  8. Post body should include a suggested category and keywords.
  9. Max height of 3 times the width.

Rules:

  1. No reactionary or reactionary-adjacent expressions. The purpose of an image is what it expresses. Some clear examples for this rule:
    • Allowed: Broken fasces, burning stars-and-bars, rotated Mussolini
    • Disallowed: Body-shaming, Pepes, gay-shaming the enemy (e.g. those pictures of Putin and Trump that libs love to post), certain hateful wojaks (even if recontextualized)
    • If you think you have touched on a grey area, see rule 7 for how to litigate this.
  2. Nothing Vaush-related is allowed
    • To be honest, I broke this rule, so it’s pretty much moot. Just run it by me first in DMs or matrix. Vaush is a bit of a dead horse, so to speak, so they’re still generally discouraged. The qualification for a viable emote referencing his existence is more a matter of execution -- @WhyEssEff
  3. No desecration of religious imagery. This includes things like burning Israeli/Saudi flag emojis. If you can modify the flags while still accurately representing countries without including said imagery, it is much preferred.
    • A grey area can be argued around whether the symbol has colloquially evolved past its religious origins (one example of this that can be relatively agreed upon is the Union Jack, which is more a symbol of colonialism if anything). See rule 7 for how to litigate this.
  4. Nothing sexually explicit or overtly horny is allowed
    • :hentai-free:
  5. No sectarianism in submissions. Pro-tendency content is fine, but we will not accept content degrading specific tendencies.
  6. No gore, no SA, no sui-bait. Nothing that could reasonably trigger a comrade.
  7. If you think you’re touching on a grey area with a submission, message @whyesseff:matrix.org to clear it before you post.
    • DISCLAIMER: Clearing does not necessarily mean that I’ll add it, just that it’s alright to submit and the rules will not be the barrier to its addition -- @WhyEssEff
  8. No content that breaks the Hexbear Code Of Conduct.

Emoji are added to the codebase periodically. Emoji may or may not be accepted and the dev team has final decision.

All images submitted must be ones you have the right to share with the project. By posting images in this comm, you are agreeing that you have permission to share this image with the project.

Hexbear Code Of Conduct, ToS, Privacy Policy, etc all still apply.

WhyEssEff’s makeshift emote repository mirror on her personal github.

Community stats

  • 312

    Monthly active users

  • 1.9K

    Posts

  • 4.7K

    Comments