The enterprise grade hCaptcha[1] is not free either. Does anyone have pricing information? [1]: https://www.hcaptcha.com/#plans
It says it's free for non-enterprises .
Moving from reCAPTCHA to hCaptcha
11–20 of 200 posts
Re: Moving from reCAPTCHA to hCaptcha
#12> But, sometimes, when we're not 100% sure if something is malicious or good we issue it a “challenge”. I think they meant “bot or human”, not “malicious or good”. Bot != malicious. And these challenges will do no good to non malicious bots.
I think you're confusing intent with implementation.
You're right that the implementation excludes non-malicious bots and fails to solve for malicious humans, but that just makes it an imperfect implementation of the intent: which is to differentiate malicious & good.
Re: Moving from reCAPTCHA to hCaptcha
#13What I don't like is that Buster doesn't work with hcaptcha...
But I don't live in a shitty country so very very rarely do I get captchas from Cloudflare.
Re: Moving from reCAPTCHA to hCaptcha
#14It's a start. reCAPTCHA is a notorious pain in the arse for anyone whose browser isn't Chrome and for anyone who doesn't keep cookies. I'm not sure if hCaptcha will be better, but it's hard to imagine it being any worse.
Re: Moving from reCAPTCHA to hCaptcha
#15[deleted]
Re: Moving from reCAPTCHA to hCaptcha
#16hCAPTCHA looks interesting, although it seems they use Blockchain for no real reason compared to just storing the payments as rows (i.e what they gain from being chained on top of another)
The point of a blockchain is that to edit an earlier record, you would need to edit every record that comes after (due to storing a hash of the previous block in the current block). However, it doesn’t make sense when one entity controls the entire system because if a hacker (or even an insider) can change one record, they could change all of them. Hence why a good blockchain would be distributed. Then, if one node edits the history, the other nodes will see the anomaly and ignore that node.
This is also why Git’s history is easy to edit when it’s only on your machine. But once you push to GitHub and others clone your repo, it becomes a lot harder to edit history. Yes, Git isn’t a blockchain, but it does use the idea of hashing the previous “block” (commit) and storing it in the current “block.”
Re: Moving from reCAPTCHA to hCaptcha
#17> "Earlier this year, Google informed us that they were going to begin charging for reCAPTCHA. That is entirely within their right. Cloudflare, given our volume, no doubt imposed significant costs on the reCAPTCHA service, even for Google." Even in the article they say... "Google provided reCAPTCHA for free in exchange for data from the service being used to train its visual identification systems." ... I thought thi…
Seeing that reCAPTCHA v3 doesn't use endless streams of images any more, I would guess that Google no longer benefits much from having users tag storefronts, traffic lights, buses or fire hydrants. Maybe their image recognition algorithm is past that stage.
Re: Moving from reCAPTCHA to hCaptcha
#18> "Earlier this year, Google informed us that they were going to begin charging for reCAPTCHA. That is entirely within their right. Cloudflare, given our volume, no doubt imposed significant costs on the reCAPTCHA service, even for Google." Even in the article they say... "Google provided reCAPTCHA for free in exchange for data from the service being used to train its visual identification systems." ... I thought thi…
Pure speculation, but at some point your dataset is large enough.
The original reCAPTCHA corrected errors in scanned books published decades/centuries ago. At some point, they're all fixed.
Similarly, more recent images have all been of traffic images. And they probably have way more than enough now -- at least of the type that can be done by reCAPTCHA.
So unless Google comes up with a new mass-categorization problem easy enough for literally everyone to do and simple and small enough to fit in a reCAPTCHA... then they charge.
Re: Moving from reCAPTCHA to hCaptcha
#19hCAPTCHA looks interesting, although it seems they use Blockchain for no real reason compared to just storing the payments as rows (i.e what they gain from being chained on top of another)
The point of a blockchain is that to edit an earlier record, you would need to edit every record that comes after (due to storing a hash of the previous block in the current block). However, it doesn’t make sense when one entity controls the entire system because if a hacker (or even an insider) can change one record, they could change all of them. Hence why a good blockchain would be distributed . Then, if one node…
Yup, that's my thing is that they control the entire thing. Although it could be like joke where "AI" ends up being just a bunch of "if statements".
Re: Moving from reCAPTCHA to hCaptcha
#20It's a start. reCAPTCHA is a notorious pain in the arse for anyone whose browser isn't Chrome and for anyone who doesn't keep cookies. I'm not sure if hCaptcha will be better, but it's hard to imagine it being any worse.
By now, I almost immediately close a page with a reCAPTCHA, because the stream of buses, traffic lights, and cycles never seems to end when you're using Firefox. And then it says "too many requests from this computer" and refuses to continue.