@jayycox
I thank you for your response, and I will not lengthen other points, so as not to appear rude to some people on the development team. But I would like to ask attention you for a point that I considered critical regarding support.
When I met the raiblocks, it was through the site "claimers.io", because I am always researching and testing sites involved with cryptocurrent, and I have been following some icos that I consider interesting.
And then I thought about dividing my claims time with a friend, and then I asked here in the forum about team, and they told me that it was enough to only share the same address.
But that leaves a question ... how to control the exact number of claims for a fair division of the prize?
So I looked for your support channel.
I had clarified that I was creating a system to be able to control the number of claims, and that it could perform an automatic division based on the number of claims of each.
But I had not found any way to track the claims, and I had already studied the "pool code" on your site and found nothing of the sort.
I received as an answer from an admin in the group: "pool is forbidden, these your question refers to a prohibited practice". And everything I typed was deleted
And then I replied: "If pool is forbidden, why the source code to create pool, is available on the official website? I recommend an update in the section of the site."
I also commented that I was not trying to create a pool, but a way to track the claims.
Then I received the answer: "This channel is for support of the" raiblocks "and not for the" faucet ". And everything I typed was deleted again.
And then I commented: "This is the support channel available on the official website and in the "faucet", if you can does not respond with "faucet" integration, I recommend to remove your "support channel" from the "faucet" site."
And everything I typed was deleted again. And I was ignored!
The best way to get involved in raiblocks is by doing something, write code, design a logo, make something - actions speak louder then words
It is really difficult to show a code, when development issues are handled in this way ... And the site does not have api information, or integrations ...
I actually got discouraged in developing any line in github after that treatment.
Another day in the" telegram group", I was talking about the problem of the bots, and I said that if it continues then the coin will end up becoming worthless. And the solution would be another cryptocoin. And I was banned of group!
With that kind of behavior of those who should listen, and help others. It's really hard!
In fact this behavior arouses contempt of many, and even comes to be grounds for attacks of "DDOS" for others.
We live a reality that BOTs can no longer be ignored, nor does it successfully recaptcha in this regard.
But we can control them ...
It does not matter if a person uses bots or not, as long as they do not have an advantage over a person who does not use ... Limitations are necessary, so that the bots do not exceed the "humanly possible".
And so it will have equality, because if a person can follow a bot, there will be no advantage of the bot on the person.
"60 claims per minute? team or bot only!
only 1ip per claim/minute? only bots then"
Increase the top, will not solve, increase the difficulty of the captcha will not solve. The solution is in the backend. Validations and limitations need to be reviewed in the backend.