||3 months ago|
|docs||3 months ago|
|extractors||3 months ago|
|static||3 months ago|
|views||3 months ago|
|.gitignore||5 months ago|
|LICENSE||4 months ago|
|README.md||3 months ago|
|config.example.json||3 months ago|
|extractor.js||3 months ago|
|lib.js||3 months ago|
|main.js||3 months ago|
|package-lock.json||3 months ago|
|package.json||3 months ago|
|tests.js||3 months ago|
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.
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.
- 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.