Frequently Asked Questions
- Universal Bypass bypasses templates which are used on thousands of domains and it would be impossible for me to keep a complete list of domains which are bypassed.
- You would have to get a new Universal Bypass version and accept its new permissions for each new bypass.
- Custom Bypasses would be pretty pointless if you could only create them for sites which are already bypassed.
Besides, every version of the extension is being reviewed by Google and Mozilla to make sure it's not harmful and it's open-source so everyone can independently review it.
As of Universal Bypass 12, there are two versions, seperated by a minus sign (-):
- Univeral Bypass version, e.g. 12.0.1: The version uploaded to the Chrome Webstore and AMO. In the changelog, this is used for changes which required more than a change in the injection script, and is therefore only available with an extension update.
- Injection script version, e.g. 931f2f9: The short commit hash representing the injection script version. However, not all commits change the injection script, and for practicality reasons, the changes between the most recent commit and the last extension update are squashed into a single changelog entry. A full list of commits and their code changes are available on Github.
There's a list of example links where you can see Universal Bypass in action over here.
Please tell me about websites which Universal Bypass is not yet bypassing, either via email or an issue on Github, and I'll try my best to bypass it!
You can support Universal Bypass by translating it, creating bypasses, or donating.
Contact me, either via email or an issue on Github!
Copyright (c) 2018-20 Tim "timmyRS" Speckhals