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 0f40cd223e
fix double require, improve tests
3 months ago
docs remove requirement for db 3 months ago
extractors replaced dashed-variables with camelCase 3 months ago
static remove requirement for db (2) 3 months ago
views remove requirement for db (3) 3 months ago
.gitignore add shit 5 months ago
LICENSE change license, add http server, start api and frontend, add cshort and improve various sites 4 months ago
README.md add testing, more debug logs in all extractors and lib.js, add mboost.me to docs with example 3 months ago
config.example.json remove requirement for db 3 months ago
extractor.js fix double require, improve tests 3 months ago
lib.js fix double require, improve tests 3 months ago
main.js remove requirement for db (2) 3 months ago
package-lock.json vastly improve logging & linkvertise bypass 3 months ago
package.json fix 123link and 1bit.space, add more to testing, add tests.js to package.json, improve logging in main.js 3 months ago
tests.js fix double require, improve tests 3 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

  • Add proper documentation (60% done).
    • Write more contributing information.
  • Improve frontend site.
    • Detect when the site itself is down via the frontend, like previous version.
  • Heroku (and similar services) support (with guide, if difficult).
  • Add passworded-link support.
  • Add multi-link 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.