Hello Social Coin Wallet,
well, I see your Point. But you'll have to understand all the users, too.
The username is thelinuxist, Country is Germany. As already said, I can't remember doing any brute force or guessing. I have changing IP's however, the Internet Connection I use is a private customer one with dynamic IP and forced disconnect (As in, IP is changed every 24 hours by policy of my ISP).
This put aside, my offer of my Services also applies to you. If you need another ten fingers on a keyboard, mine are readily available.
As said before, it may be an encoding problem. Was just the first thing coming up in my mind, String comparisons in PHP are (if done correctly) binary safe and, thus, bytewise - but if there is a difference in encoding, this usually isn't noticed.
Maybe the other users who are denied are also from non-english countries?
Besides, why do you bother with the traffic from blocked users (= bots) instead of telling them they're blocked and should contact support? Sounds pointless to me, it confuses legitimate users like me (and around 10 others by now in this thread) plus puts unneccessary load on your servers.
Beside all that, do you offer YouTube views from your captchas? A friend of mine is a YouTube Publisher, he might be a customer...
Currently from a WindyOS System
Thank you for getting back to me so quickly.
I was able to find your sessions being served from our ad server in your region without any issues. A session is generated when the web server your browsing reaches out to our API and requests a captcha to be displayed. In most cases this would then result in you seeing the captcha somewhere on the page but does not always mean you started or interacted with it.
20 out of your last 125 sessions were not completed, this means we did not receive a response / solution which could indicate you were surfing the page and then left, never started captcha, or simply just didnt solve it and left after it was presented. This number being rather low is helpful when debugging why a user is not being marked as correct because it allows us to see if duplicate sessions are being created and then mixed up. In this case that does not appear to be whats happening.
74 of your last 125 sessions were submitted to us and marked as correct and valid. This is great!
8 of your past 125 sessions were submitted and valid other then the fact that the answer was wrong. (when compared to some of the more obstructed text captchas this is actually rather low!)
On 12/14/2014 you submitted a captcha claim prior to the timer showing the captcha (it was blank and empty)
On 12/21/2014 you submitted an undisclosed amount of captcha tries prior to the timer showing the captcha (again these were blank and empty)
Due to the activity on 12/21/2014 (recently) your future sessions for an undisclosed amount of time were being rejected. While this might to some appear like a ban, we actually do not consider it that. Our bans are not issued for the early blank captcha solving and they do not drop off quickly, additionally they are network wide. This is rather a simple security measure to ensure the health of both our partner websites serving the captcha, our ad servers, and as a security measure to prevents bots which are attempting to solve the captcha from doing so before the timer has finished.
Because of this temporary cool down period which was triggered, your future solves were automatically marked incorrect as you previously submitted them before the timer finished. This effected your last 14 captchas.
I have already moved your cool down period to zero so that future sessions will not be effected, and I see while writing this line one of your captchas was just marked as successful.
We understand that to provide the most enjoyable experience to end-users whom are using our captcha system on a website, they would like to know the information surrounding such triggers. However our security team has taken what we call The Ghosting Approach. This is a mannerism when targeting users whom are acting in a way outside of the intended use to not be alerted when they are detected or specifically why. This is actually a practice commonly used in popular web platforms including most notably for its controversy over using their version of ghosting, Craigs List which is a popular international classified ads website.
In regards to our advertising platform, the video hosting platform used is up to the advertiser for each campaign. The majority of our advertising partners and advertising agencies which we work with have in the past selected youtube.com to be their hosting platform for the campaign they are running. Advertisers who are looking to increase their video views are not likely to be satisfied with the performance of our video captcha platform when specifically looking at the increase of youtube.com views. While advertisers running campaigns through youtube.com will likely see an increase in their view count, the increase is not an accurate reflection of the actual number if video plays and are not part of our metrics we use when calculating campaign budgets.
We love to receive feedback from both the end users and our partners serving the ads. If you would like to take a moment to PM me any additional thoughts please do not hesitate to do so. We are always working to improve the over-all usability of our captcha system. Our captcha system was designed specifically for use in the Bitcoin field, where majority of our end-users are to a certain level, technologically sophisticated. This position requires us to have certain standards of the captchas being solved as well as the ability to filter out traffic which is breaking the T.o.S. of the specific site they are on if botting is prohibited. We understand that some of our 'features' are not to be appreciated by the end users solving the captchas but it is a requirement to be able to issue payouts of nearly 400% higher then solve media, while still keeping partner websites automation free.