Kaz, my faucets get removed for being 'broken' - despite running correctly all the time. The same reporting system could (and should) be used to make sure the claim process is clear and apparent on all faucets.
We can automate checking if you site responds with HTTP 200 status (and that's what we do and what probably is taking your faucets down). We can't automate checking if the claim process is clear and apparent. That two very different problems and the same reporting system can't be used for that. It has to be manual.
Also it only applies to the Faucets list. I completely agree that scamming faucets, or faucets requiring you to click the ad shouldn't be on the list. As I said, that's something we're working on. However banning faucets from access to FaucetBOX.com API won't change anything.
So if I'm not overreacting, we both essentially agree on the same point. I posit there is an issue that could potential affect the ecosphere, while you concede there is nothing you can think that can be done.
I believe this thread should be the place to discuss the issues of Admins, as these issues ultimately trickle down to users.
Well, we're discussing it right now
. But I still think you're overreacting. What happens on some faucets won't make ad networks ban all faucets.
What I agree on is that such faucets are a bad thing. And I agree that FaucetBOX.com shouldn't have such faucets on the list. I don't agree, that we should ban access to FaucetBOX.com API.
I'm not aware of any Xapo faucets that suffer from similar issues. Perhaps it's because they have a more 'corporate' sheen to their service, but I truly believe Faucetbox should employ similar features. It improves the ecosystem. The only other faucets that scam users and potentially lead people to click ads are the shady direct payment weekly faucets and hardly anyone uses those.
I think you're missing the point. It's not "Xapo faucets" or "Faucetbox faucets" that are scamming. Most scamming faucets don't connect to any service at all. The thing is that Xapo doesn't (as far as I know) provide a publicly available and simple faucet script, while FaucetBOX.com does. So it's not the FaucetBOX.com itself that is being used to scam (as scammers don't need us, really). It's the Faucet in a BOX script that's used to scam. As the script is something you download and host yourself, we can't ban it remotely. And that is the reason why there are no Xapo faucets with such issues.
Also what exactly do you mean by "similar features" that we should employ? What Xapo do? Maybe there is some solution that I'm missing, I'd love to hear about it then
.