-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faucet Abuse #10
Comments
One more thing, possibly a cool down period of 1 minute before the faucet can send out again, that way bots can be thwarted a bit as well? |
@Focus9 automated creating new accounts is no big deal, so i do not think sending out only to new accounts will solve abuse better than it is now. You can set faucet, that one account can only claim once. Bots can not claim at all ... how would they solve the recapcha?! There are many things that could be done to restrict faucets even more, like evercookies ... but the best protection from my point of view, is the setting i mentioned above. Maybe in combination with: |
Here is another one. I hope you can incorporate this. I have noticed that they bot the faucet with new accounts. The other faucet software which was around a while ago blocked the tor network. Is it possible you can do the same? https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=1.1.1.1 to find out the TOR exit nodes to your server and then we can block those IPs from accessing? |
@Focus9 Having a ip blacklist is surely a good idea, i would rather block goverment ips than tor exit nodes ... buts thats up to the maintainer than :-) Meanwhile you can use peerblock or other 3rd party software to prevent ips or ip-ranges to access your faucet. |
Hi Luxe |
@eljoj does not work with php, sry ... |
Hi luxe, Is it possible for you to modify the faucet code so that it will only send to an account that has never had a transaction and also limit by IP?
The text was updated successfully, but these errors were encountered: