[Feature Request] Bot enabled emojis - Standarized by service : Emoji Replacer By Service

La issue non nomina file, test o punti di ingresso. Inizia mappando il percorso di invio del bot e le integrazioni con le piattaforme, quindi definisci l’archivio dati di sostituzione e un interruttore che funzioni senza riavviare; il completamento deve includere sostituzioni specifiche per piattaforma, con un fallback alla parola invariata quando non esiste alcuna mappatura.

I'd be willing to submit a PR with a standardized Emoji "Polling" piece to standardize the emoji use across platform. Meaning if the bot wants to add a smiley that is not standardized across the platforms it will be able to lookup in a [data table / json / xml] Data Store for the correlating information to send to the different systems so that a compariable smiley is presented on the different systems.

for example: when presenting Kappa as to express a mistake or frustration, in Twitch Kappa is well known but in Mixer it doesn't exist, in Discord (I actually don't know, I dont' use Discord all that much) but what would happen in the application is when the bot attempts to send the phrase "This didn't work like I thought it would Kappa" that the app would do is go to the data store and lookup the keyword "Kappa" in the data table and for each "Send" to the different systems it would replace "Kappa" with the corresponding keyword or phrase. if it doesn't find a result for the system it would not replace the word (as Kappa has an almost universal meaning if your on any streaming service)

Pre Project Discovery and Limitations/Concerns and thoughts

1. Plugin style Extensions for inclusion of this type of software "Part"
   a. my assumption is that the "Emoji Replacer" would / should be a secondary piece outside of the bots normal function. what I really mean is that this "Feature" should be Togglable, (able to turn it off with a switch, without restarting the application.
2. Toggleable feature. (should be able to turn off without restarting the application: thus the plugin concept from step one.)
3. Nice To have is a Mapping table: Keyword -> Platform -> Emotional Conveyance -> Platform Equivalence
4. Lots of Work. the command pathway for sending would need to be "Interrupted" giving way to a possible huge performance hit and other currently unknowable issues.

!!Important!!
5. Question: would something like this be useful, I would LOVE for a bot i use regularly to convey even the slightest "Emotion" and emoji's are a start.