It's a little worse than that. The wallet id you are referring to belongs to the user name "BitPotato". I was on for a good part of the day yesterday/last night. They got every reset potato!
Yeah that guy's a real tool (lolol)
A captcha or daily quota per ip would save customers and your business bitpotato, you have to realise this.
While your moral crusade against 'Guzer' seems to be a little extreme, do realize the following:
- I use that address for BitPotato, CoinBomb, LTC Treasure, and other gambling games. Yesterday I won two potatoes, one of which did not sell. Today, I won a cheap spud, and am likely going to lose the Gold potato today, since someone is locking it out to prevent buyers.
- A more eloquent solution to the botting problem would be to give each address a cooldown. Have it so it can only be clicked every 100ms, and anything more wouldn't be accepted. Basically anything other than requiring a captcha. Those are frustrating to fill out themselves, let alone with a race to finish it.
- A program to auto-fill a captcha is an easy enough feat, and would only increase the distance between botters and clickers, easily destroying the website's thrill.
Exactly. Thank you for your input. The issue is that there are services and programs that will fill captchas, and if we use a captcha system even if it is all users competing, it's a race to fill out the squiggly letters to get the potato. We used to have a click limiter on the potatoes, but we realized it was only making it harder for legitimate users to get the potato over botters, so we've removed it. We're still working on Version 2 of the site. We've experienced a lot of delays, mainly that our backend programmer is still attending college. We plan to implement a sort of sub-captcha system, that will require input before you actually grab a potato. We're also still looking vigilantly into potatoes responding to multiple users with the send addresses. When a potato gets locked, only one user should receive the "Potato is almost yours!" message. From recent emails we fear this bug may still be occurring on a smaller scale. We're setting up a distributed test network to test hammering the server for requests on locking down a potato.