Giter Club home page Giter Club logo

fakegeobot's Introduction

$$\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: -10; position: fixed; top: 0; left: 0; height: 100vh; object-fit: cover; background-size: cover; width: 130vw; opacity: 0.5; background: url('https://avatars.githubusercontent.com/u/87614587?s=400&u=43f27da8fdaa2870e8c47969a7e900b797d9ff9d&v=4');]{x0000}$}$$

fakegeobot's People

Contributors

dependabot[bot] avatar michael2to3 avatar snyk-bot avatar spechide avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

Forkers

saber13812002

fakegeobot's Issues

Check for Active Schedules

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.

User-triggered Schedule Change and Flood Protection

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.

Not always automatically sending messages to users

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.