I'm curious how you plan to avoid/circumvent the inevitable hard IP ban that the largest (and most sought after targets) will place on you and your services once you begin to take off? I could have really used a service like this just yesterday actually, I ended up fiddling around with iMacros and got about 80% of what I was trying to achieve.
It's a great question. What we're really trying to do is make data accessible programmatically and at scale. We want to connect data providers and data consumers with APIs in a way that's mutually beneficial vs. being a tool for data theft. Our hope is to (once we scale) actually work with data providers directly on the on the distribution of their data so the IP ban becomes a non-issue.
Show HN: Kimono – Never write a web scraper again
231–234 of 234 posts
Re: Show HN: Kimono – Never write a web scraper again
#232Earlier quoted context omitted.
So because it's written in LISP it gets a free pass in other areas? That seems like a dubious claim.
No, despite it being written in an obscure language and sparse UI it has massive traction anyway. There's a lesson in there somewhere.
The website that lets technologists hang out with people who might give them large sums of money to see their ideas succeed doesn't have to be good, or pretty.
If the website were better, or prettier, that would not add any additional value to the previously mentioned large sums of money.
(Oh, and advice, and being able to chat with industry leaders and experts on diverse arrays of topics, etc.)
Re: Show HN: Kimono – Never write a web scraper again
#233Re: Show HN: Kimono – Never write a web scraper again
#234Earlier quoted context omitted.
I hope that the lite plan will feature auth handling, I can't imagine the service being useful in most cases without it.
We're working on auth... it's the most requested feature at the moment. And we're still beta at the moent, so all usage is free