31–40 of 84 posts
For a case with lots of requests how does Autotab handle ip-blocking? Does each run use a different portal instance?
This is awesome. I was just trying to get a rudimentary version of this for some "user" interaction heavy data extraction. Definitely giving it a try. For a case with lots of requests how does Autotab handle ip-blocking? Does each run use a different portal instance?
I see it's able to perform data extraction, but what if you wanted to enter in data from another system, or generated by an LLM during the workflow?
This is awesome. I was just trying to get a rudimentary version of this for some "user" interaction heavy data extraction. Definitely giving it a try. For a case with lots of requests how does Autotab handle ip-blocking? Does each run use a different portal instance?
When you run Autotab in the app it runs locally, so no IP blocking issues there. If you want to run it in the cloud eg via API, by default your IP will be from the data center but we have residential proxies that we can enable on a case by case basis.
Who is your vendor for residential proxies? That’s quite a sketchy industry.
This is awesome. I was just trying to get a rudimentary version of this for some "user" interaction heavy data extraction. Definitely giving it a try. For a case with lots of requests how does Autotab handle ip-blocking? Does each run use a different portal instance?
When you run Autotab in the app it runs locally, so no IP blocking issues there. If you want to run it in the cloud eg via API, by default your IP will be from the data center but we have residential proxies that we can enable on a case by case basis.
Earlier quoted context omitted.
When you run Autotab in the app it runs locally, so no IP blocking issues there. If you want to run it in the cloud eg via API, by default your IP will be from the data center but we have residential proxies that we can enable on a case by case basis.
Just tried it - very cool indeed. I did a page loop extraction but it seems to be the same speed when I run it. The elements I am doing the loop on look pretty much the same, just different images. I think it would be great if it was able to generalize how to find an element like with css selectors for example to speed up once its sure that is the data you are looking to extract for a given loop.
This is awesome! What is your most common use case? Have you thought of competing with https://scribehow.com/ in the documentation space?
Haven’t done a lot with Scribe-like documentation cases. Given the pace at which this technology is developing we’re focused on making Autotab really good at the most economically valuable tasks.
Earlier quoted context omitted.
When you run Autotab in the app it runs locally, so no IP blocking issues there. If you want to run it in the cloud eg via API, by default your IP will be from the data center but we have residential proxies that we can enable on a case by case basis.
> we have residential proxies that we can enable on a case by case basis. Who is your vendor for residential proxies? That’s quite a sketchy industry.