DevChatter / DevChatter/DevChatterBot

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

オープン
#108 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
JavaScript
スター
54
フォーク
24
PR マージ指標
30日以内にマージされた PR はありません

説明

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.

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

この issue ではファイル、テスト、エントリポイントが指定されていません。まず bot の送信経路とプラットフォーム統合をマッピングし、次に置換データストアと再起動なしで機能する切り替えを定義します。完了時にはプラットフォーム固有の置換を含め、マッピングが存在しない場合は単語を変更せずに使うフォールバックにします。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
javascript
領域
backend
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。