Re:Mechanical Turk Lessons Learned
by ayw on Wednesday February 01, 2017 @03:07PM
(#13544556)
Sorry to hear about that experience. You should consider using Scale API (www.scaleapi.com). This is a perfect use case for our data collection API: https://docs.scaleapi.com/#create-data-collection-task
[ Parent
| on HN ]
Why does the "Scale" logo on this page not link to your home page? From that API documentation page I have no context about what Scale API is or what it does. The "Introduction" page isn't even that helpful if I've never heard of you before.
All that said, Scale API seems like a nice alternative to Mechanical Turk for some kinds of tasks.
Re:Mechanical Turk Lessons Learned
by freehunter on Wednesday February 01, 2017 @03:56PM
(#13545073)
It's a fair point. Lots of documentation pages or company blogs don't link to the company's main website, and it's super annoying.
We're working on redesigning and cleaning up all of our pages! Sorry about that
Very interesting. I will keep this in mind since we do have another 10,000 or so jobs that we'll need completed in the next while.
The pricing page isn't totally helpful. I'm not sure if I would fall under `Comparison $0.10` or `Data Collection $0.25/minute`... or if many of those prices apply to a single job.
Either way, I'll keep your product in mind.
Re:Mechanical Turk Lessons Learned
by brilliantcode on Wednesday February 01, 2017 @06:00PM
(#13546278)
Tbh I found scaleapi to be quite expensive, much more than implementing your own QA process on Turk. Also if scaleapi goes down you have to do the work all over again. Scaleapi is nothing new, there have been others before but they were gone as quickly as they came, and suddenly all the API code stopped working.
It was a bad enough experience that I'd never base my mission critical product on a 3rd party startup. Amazon could go bad too but a small startup it's almost expected.