Intro to Bypasses
Don't waste your time with compliance. FastForward automatically skips annoying link shorteners.
This section will show you how to write bypasses for FastForward, which you can then submit in a Pull Request!
While the Custom Bypass section in the extension settings is perfectly fine for making a lone bypass, making many bypasses will require you to have these skills and tools:
- Basic knowledge of JavaScript and HTML
- IDE/Code Editor
- Visual Studio Code is an excellent free IDE for web development
- Webstorm is a paid IDE for web development that has many excellent features (free for students)
- Internet browser which allows sideloading extensions
- Google Chrome and Firefox Developer Edition are preferred because these are based on the 2 types of browsers that we create the extension for
- Knowledge about Git and Github (PRs, squash and rebase commits, Github Actions, etc.)
- Knowledge about different coding styles used in web development
- Node.Js
- Git (MUST HAVE)
- Github Desktop (OPTIONAL but nice if you are not accustomed to Git on the command line)
- A personal fork of this repository
- OPTIONAL but useful: A virtual machine to test new bypasses (any development versions of FastForward will not affect your main extension) and to protect your PC against any unsavory sites
- VMWare Workstation Player is a free virtual machine software that works well for testing
- Windows Sandbox on Pro versions of Windows 10/11 works well for a clean slate every time
- Make sure to follow the code style set in CODE_STYLE.md
- DO NOT make bypasses for NSFW sites, this could remove our extension from web stores; we will not merge bypasses for NSFW sites
- Before making a bypass, make sure that you aren't creating a bypass that's already there (Ctrl + F)
- For mv2 bypasses, check the injection-script.js file
- For mv3 bypasses, check the bypasses folder