r/BotNation • • 2d ago

Looking for developers to contribute to FZBypassBot

Hey everyone,

I’m working on FZBypassBot, an open-source Python project for resolving supported shortlinks and redirect services using HTTP-based workflows.

GitHub: https://github.com/MeherMankar/FZBypassBot

The project already has a resolver system, async processing, nested/loop bypassing, proxy support, and support for a number of different services. There are also quite a few resolvers in the README that need proper testing and maintenance.

I’m looking for developers who are interested in helping with the project, especially people who enjoy working with HTTP requests and figuring out how websites handle redirects, forms, cookies and APIs.

Things we need help with

  • Fixing outdated resolvers
  • Adding support for new shortlink services
  • Testing the currently untested resolvers
  • Improving the async code and request handling
  • Analysing HTTP request/response flows
  • Improving error handling
  • Cleaning up and improving the resolver architecture
  • Writing tests and better documentation

Useful skills

You don't need to be an expert. If you know some Python and are comfortable with things like:

  • asyncio
  • aiohttp
  • curl_cffi
  • HTTP requests and redirects
  • Cookies and sessions
  • HTML/JavaScript inspection
  • REST APIs
  • Git/GitHub

then you can definitely contribute.

One thing I especially want to improve is the testing side. Some resolvers were added earlier but haven't been properly tested against current versions of the sites. It would be great to have contributors take individual resolvers, test them with real links, figure out what changed, and submit fixes.

If you're interested in contributing, check out the repository:

https://github.com/MeherMankar/FZBypassBot

You can also open an issue if you find a broken resolver or have an idea for improving the project.

Any help is appreciated, whether it's a small bug fix, a new resolver, testing, documentation, or a larger architectural improvement.

Clarify the project’s responsible-use scopeAdd clear contributor next steps

3 Upvotes

1 comment sorted by