aboutsummaryrefslogtreecommitdiffstats
path: root/doc/mod/notification-matrix.d
diff options
context:
space:
mode:
authorGravatar Christian Hesse <mail@eworm.de>2023-02-03 20:29:10 +0100
committerGravatar Christian Hesse <mail@eworm.de>2023-02-03 21:59:26 +0100
commit8a900dce00bf08acc1347ff9befedd634ee76adb (patch)
tree2c2c23dbdb38dae32095c7dd899701fb49c6734f /doc/mod/notification-matrix.d
parent4bc5b9cf5f705600bdaacf439fb36737fb33729e (diff)
telegram-chat: delay confirmation of updates
Several devices can communicate with the same bot, and we want all of them to receive their updates. However this can be tricky, as... * ... sometimes internet connection can be unreliable or saturated. * ... device can be busy with long running command. * ... the Telegram bot api servers seem to implement what ever kind of rate limiting. Anybody can give details? So let's confirm the update id after third request only. 😁 This gives delayed devices some extra chances to catch up.
Diffstat (limited to 'doc/mod/notification-matrix.d')
0 files changed, 0 insertions, 0 deletions