Modular server-side link protector bypasser. https://bifm.tacohitbox.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
aria 89b39b6c57
update deps
1 month ago
docs fix 1bitspace, improve gplinks, fix older node issues 4 months ago
extractors fix vuln 1 month ago
static fix frontend issue with date 5 months ago
views fix other mistake 4 months ago
.gitignore add shit 7 months ago
Dockerfile reorganize lib kinda, remove run.sh completely 4 months ago
LICENSE change license, add http server, start api and frontend, add cshort and improve various sites 6 months ago
Procfile Add Features 5 months ago
README.md add link1s.com 5 months ago
config.example.json migrate to got 5 months ago
extractor.js fix double require, improve tests 6 months ago
heroku.yml migrate to playwright / remove tei.ai / fix gplinksextractor / improve lib slightly 4 months ago
lib.js fix vuln 1 month ago
okteto-stack.yaml Add Features 5 months ago
package-lock.json update deps 1 month ago
package.json fix 1bitspace, improve gplinks, fix older node issues 4 months ago
run.js migrate to playwright / remove tei.ai / fix gplinksextractor / improve lib slightly 4 months ago
server.js fix vuln 1 month ago
tests.js add additional domains to aylink.co, add less questionable link 4 months ago

README.md

BIFM

A modular, easy to use, server-side link bypasser.

Why is server-side better?

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.

Licensing Notice

Since this commit, this rewrite is using the APGL license, meaning that BIFM now requires attribution if you are using BIFM as an API, docs of which are coming shortly. If you would rather use the Unlicense version, use this commit and behind.

Roadmap

  • Optimize puppeteer extractors, espescially aylink and exeio.
  • Improve frontend site.
    • Add dark mode.
  • Add back proper Heroku support.
    • Improve the 30 second rule (requests cannot take longer than 30 seconds w/o timing out) with it.
  • Add referer support.

Sites being planned

There's a general need on our part to support all sites that previously were supported, but these are also some we would like to get done.

  • mirrorace.org