Improved handling of upstream disconnections #4

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

Currently, a TG user will be kicked from the group chat if they encounter some fatal problems (e.g. bad nick / NMDC $ValidateDenide [sic]).

But there are other kinds of fatal problems that are less easily autodetected (e.g. nick whitelist, or, custom Hub-Security warnings).

There should be some way of detecting other fatal problems with the hub connection, and dropping the TG user accordingly.

  • Check if the hub connection has repeatedly disconnected in a certain time interval?
  • Check if messages from other TG users aren't reflected down this hub connection?

But both of those require multiple hub connections, at least one of which is valid, to use as an oracle.

Currently, a TG user will be kicked from the group chat if they encounter some fatal problems (e.g. bad nick / NMDC `$ValidateDenide` [sic]). But there are other kinds of fatal problems that are less easily autodetected (e.g. nick whitelist, or, custom Hub-Security warnings). There should be some way of detecting other fatal problems with the hub connection, and dropping the TG user accordingly. - Check if the hub connection has repeatedly disconnected in a certain time interval? - Check if messages from other TG users aren't reflected down this hub connection? But both of those require multiple hub connections, at least one of which is valid, to use as an oracle.
Sign in to join this conversation.
No Milestone
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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