How the priority and Limit works in R87

Since the release of FaucetInABox R87 I've got many questions about how the new "shortlink" feature works. I'll try to explain it here.

Let we say you have 5 shortlink providers A, B, C, D, F.

A has CPM of $3, B and C have CPM of $1.5 and all they pay for unique visitors (once every 24 hours).

D and F pay for all the traffic they receive.

We need to push "A" in the first place. And limit to once per day:
- A - Priority 100 Limit 1

Now we don't care if "B" or "C" will be next.
- B - Priority 50 Limit 1
- C - Priority 50 Limit 1
(they will be chosen randomly)

And finally:
- D - Priority 10 Limit 0
- F - Priority 10 Limit 0
(they will be chosen randomly)

The Limit is per IP only. So if your users have dynamic IP you will benefit from that.

If any API call fails then it will fall-back to the next.

If your shortlink is required then you always need to have at least one "Limit 0" shortlink service. If FBU gets to the end of the shortlink services list and there is nothing to display then the "requirement" will auto-disable for that user.
If you want to limit the daily claims there are other methods.




Other topics:
Faucet In A Box Ultimate R96 is here



I'll try to be short this time.

Changelog:
- Added 7 days IP check local cache - should allow ...


Faucet In A Box Ultimate R117



Changelog:
- fixed "Undefined index: usertoken" bug

Download:
faucetinabox-ultimate-r117.zip

Upgrading ...


Faucet In A Box Ultimate R118

Changelog:
- PHP 8.2 compatible
- Removed dead captcha providers
- Removed dead wallet providers
- ...


Faucet In A Box Ultimate R99



Changelog:
- FaucetHub - HORA Token (HORA) and TRON (TRX) added
- ExpressCrypto.io added (experimental, ...


Faucet In A Box Ultimate R100



Changelog:
- "Packets out of order" when installing bug - fixed
- USD conversion to some exotic ...