-
Notifications
You must be signed in to change notification settings - Fork 12
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom aliasing :words: to an emoji/custom emoji #878
Comments
@lampholder The original request is that |
If I may add a use case for this: I want to see this for chat rooms. Many bulletin boards have a special set of emoticons which are not covered by emojis. These often are animated GIFs, user write them in the middle of a sentence (or after it ;-). [I'm not talking about stickers.] Riot can view inline images but AFAIK you need a long markdown phrase to do that, including the URL to the image. No single chat room user wants to write that every time so it would be great if aliases for text input were possible. |
It wont happen unless you make the integration yourself |
Right, I've brutally reshaped this issue to address the :custom_words: -> emoji/custom emoji usecase. The Halfshot diversion @turt2live summarised with:
can be created as a new issue if anyone feels keen, but know that if you do I'm going to class it as a P5 Feature request 😛 |
I always end up with features there :( |
+1 for this, custom emotes are always great to have. I've implemented a very simple and hacky version that just replaces Here are the changes I made to get this working: https://github.com/mserajnik/riot-web/commit/0f398ad38d203c0aa89834c5694ef1d8b2e1da62 To serve the emotes, I've created a small emote server application: https://github.com/mserajnik/emote-server Disclaimer: I've made this to be used by me and my friends. We run a private Synapse server with federation turned off and trust each other. I'm not that familiar with React, so I'm not sure if my Therefore this should merely serve as an example of how it could be done in terms of the general workings (having emote packs served or installable, users need the same packs to see the same emotes) and I do not recommend usage of this modified version of Riot or the React SDK (and the Apache License 2.0 applies, so I obviously provide no warranty if you do decide to use it). |
This is possible, although you need to hotpatch the emojibase-data dependency before building riot. Not a great solution but I doubt riot will provide an official way to do it |
+1 from me. This would be so useful to have in the UI under the user's personal settings. Especially since the official emoji shortcuts are quite often really counter-intuitive. I keep typing ":dino:" over and over and am disappointed time and again, that there's no dinosaur. But, contrary to popular belief, they haven't suddenly become extinct but are alive & well under ":sauropod:". This is the secret part of Jurassic Park no one told you, right? ;-) |
Well under the recent change all emoji descriptions were changed (to some other system which can be surely justified and this is out of my scope now anyway), so people trying to access them by the old and known words fail; this make this issue pretty actual again. What I imagine is that emjois can have undefined amount of aliases (and if it's matched within the string it may be simply a concatenated string of names) so people can use the old name, the new name, or whatever name scheme they prefer (or even use a shared name scheme from others). For example I always look for "sad" and now it doesn't find any of the "frown" variants. (Funnily I would never use the word "frown" for a sad face, but that may be my lack of vocabulary.) |
Other clients like Cinny, Nheko, Fluffychat etc. support custom emojis. Is this planned for Element? Not sure if this is the correct issue since I didn't find anything else that mentions custom emojis. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
No description provided.
The text was updated successfully, but these errors were encountered: