Currently, our "Telegram Fake Location Bot" allows users to change the schedule for sending fake location data very quickly, which can potentially trigger flood protection mechanisms on the receiving end. We need to implement flood protection and limit the frequency of user-triggered schedule changes to prevent this from happening.
Propose implementing the following changes to address this issue:
Implement flood protection: We will limit the number of schedule changes a user can make within a certain time period to prevent triggering flood protection mechanisms on the receiving end.
Limit the frequency of user-triggered schedule changes: We will add a cooldown period between schedule changes to prevent users from changing the schedule too frequently.
Noticed that is still trying to send location data even after the user has deleted the scheduled messages. Need to implement a check to ensure that the bot only sends location data when there is an active schedule in place.
We propose implementing the following change to address this issue:
Check for active schedules: Will add a check to ensure that the bot only sends location data when there is an active schedule in place. If the user has deleted the schedule, the bot will not attempt to send any location data.
The bot uses its own cron job and multiprocessing/threading libraries to send messages to users. However, it appears that for random users, the bot is not functioning as intended and not sending messages automatically. This issue is likely related to the functionality of the cron job and multiprocessing/threading libraries.
To address this issue, the code of the bot should be reviewed thoroughly to ensure that the cron job and multiprocessing/threading libraries are functioning correctly. It may be necessary to test the bot with a small group of users to identify any errors or bugs in the code. Additionally, the Telegram API documentation should be reviewed to ensure that the bot is properly connected and that there are no issues with the API.