Rewrite of bypass-it-for-me, a server-side link bypasser.
Go to file
2022-05-20 18:56:40 -04:00
extractors fix linkvertise, add thing hazy wanted me to 2022-05-20 18:56:40 -04:00
.gitignore add shit 2022-05-04 12:53:43 -04:00
config.example.json add shit 2022-05-04 12:53:43 -04:00
extractor.js add shit 2022-05-04 12:53:43 -04:00
lib.js improved ouo, added sh.st, lnk2, ity.im, social-unlock and boost.ink 2022-05-20 00:43:30 -04:00
LICENSE Initial commit 2022-04-10 03:47:39 +01:00
main.js fix linkvertise, add thing hazy wanted me to 2022-05-20 18:56:40 -04:00
package-lock.json add shit 2022-05-04 12:53:43 -04:00
package.json add shit 2022-05-04 12:53:43 -04:00
README.md fix linkvertise, add thing hazy wanted me to 2022-05-20 18:56:40 -04:00

bifm

Bypasses link protectors server-side. Now with more sites and easier to develop for.

why server-side?

Fetching the pages from the client requires sending some information about your device to the tracking server (HTTP headers, IP address). For obvious reasons, this is not a great solution. It defeats the purpose of bypassing tracking links. By using a server-side solution, information about your client are never sent to these tracking servers, unless you explicitly want to.

supported sites

  • ouo.io/.press
  • boost.ink & aliases
  • ity.im
  • sh.st & aliases
  • social-unlock.com
  • lnk2.cc

sites being worked on

  • linkvertise & aliases