Action messages are reflected for TG users #9

Open
opened 2018-06-24 02:22:48 +00:00 by mappu04 · 0 comments
Owner

The hub connection cannot natively distinguish between an action message (e.g. /me) and a system connection message (e.g. * Register your nick!).

A heuristic is used to detect this case when a hub user posts a /me message, and convert it into a TG message.

However, there's no detection for the reverse case. A TG user can post a /me message, and while TG does not convert it into an action message, it gets reflected through the hub connection and erroneously re-appears in the TG channel.

The hub connection cannot natively distinguish between an action message (e.g. `/me`) and a system connection message (e.g. `* Register your nick!`). A heuristic is used to detect this case when a hub user posts a `/me` message, and convert it into a TG message. However, there's no detection for the reverse case. A TG user can post a `/me` message, and while TG does not convert it into an action message, it gets reflected through the hub connection and erroneously re-appears in the TG channel.
Sign in to join this conversation.
No Label
bug
wishlist
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: code.ivysaur.me/nmdc-telegramfrontend#9
No description provided.