It isn't just a search engine. It's also a link monitor. Someone somewhere is linking those pages. It might not be a current user, but they still crawl it in case the person with those bad links signs up.
The main point of this article is that you can pay humans to solve CAPTCHAs, via a company which acts as middle-man.
The company in question (Kolotibablo) has a website at https://kolostories.com/ which argues that paid CAPTCHA-solving is a good economic option for the people who do it. Maybe it is? I can't decide.
I wonder if there's some architectural reason for using `["Status", {}]` shapes instead of a more traditional response shape
[
"Ok",
{
"data": {
It seems to place a lot of the error detection burden upon the caller, since the response can be empty `[]`, it can have a status without a body (which, I guess may be fine for their api?) `["OkHarHar"]`, and then the usual promises-made-promises-kept of the expected keys being in the `response[1]` location. One can see this heartache sort of play out in the subsequent python code in the blog post although they just return None in the simple `len() != 2` case
20 comments
[ 189 ms ] story [ 5853 ms ] threadSource: My server logs.
They have some info on their Data[0] page.
I always saw them as - if Google Search had a public back-end UI, then Ahrefs would be it.
[0]: https://ahrefs.com/big-data
The company in question (Kolotibablo) has a website at https://kolostories.com/ which argues that paid CAPTCHA-solving is a good economic option for the people who do it. Maybe it is? I can't decide.