You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assume a scenario where the user starts the telegram bot twice a day within, that is less than 24 hours. That would mean that with our current logic, the user will get the same tweet, again and again, showing duplicates at the telegram bot level.
Hence we need to find a way to resume sending tid to telegram bot only after the last send tid before stop command was executed for a particular user.
An ideal solution would be to store the last received tid at the telegram cache.
The text was updated successfully, but these errors were encountered:
Assume a scenario where the user starts the telegram bot twice a day within, that is less than 24 hours. That would mean that with our current logic, the user will get the same tweet, again and again, showing duplicates at the telegram bot level.
Hence we need to find a way to resume sending tid to telegram bot only after the last send tid before stop command was executed for a particular user.
An ideal solution would be to store the last received tid at the telegram cache.
The text was updated successfully, but these errors were encountered: