Glossary

Request Repeating - Most advanced filters will repeat the same requests that the user sends to the site. They are aware that some systems are locked behind log-ins.
- Extension-based Request Repeating - This is the worst-case scenario for us, because it allows the extension to bypass Network Fingerprinting with Link Bot Locking, by replicating the request in the extension, since it would have the same User Agent and IP. They might do the filtering on the extension or send the data to their own API's, similarly to how some filters check HTML Content for reactive sites. The good news is that this won't block it for everyone else using the filter globally or in your district, since the data would be able to be spoofed to get any site blocked maliciously, but it is an annoyance to the usser. The only way to bypass, if it ever becomes a problem, is to apply the encoding mechanisms in the Filter Lock config and from there on it is an endless cat and mouse game.

Raffesia calls this "Imitate Probing"

Wrapping - Storing code in a weird way or exceedingly standard way that the filters won't pick up on. See this doc

Filter Lock-specific

methods - These help to prevent manual blocks
modes - When I say this I refer to the optional features that are not methods. These are made to prevent filters from automatically blocking the links, rather than locking them down to students.
demo (main) links - Links that aren't protected by Filter Lock and are mainly used for showcasing the site
per-server staff - This means staff in the proxy community's Discord server that have permission over the bot. It's usually used to make a distinction from the proxy bot hoster.
Types of tokens
- Sync Token - See this doc
- Access/User Token - See this doc

The lists are ordered by importance