Earlier quoted context omitted.
I would be interesting if you can find it.
https://antoinevastel.com
Show HN: Finic – Open source platform for building browser automations
71–79 of 79 posts
Re: Show HN: Finic – Open source platform for building browser automations
#72Earlier quoted context omitted.
What would you recommend for parsing instead?
In this specific scenario, where the project is using *automated Chrome* to even bother with the connection, redirects, and bazillions of other "browser-y" things to arrive at HTML to be parsed, the very idea that one would `soup = BeautifulSoup(playright.content())` is crazypants to me I am open to the fact that html5lib strives to parse correctly, and good for them, but that would be the case where one wished to us…
Re: Show HN: Finic – Open source platform for building browser automations
#73Earlier quoted context omitted.
Thanks! Wasn't familiar with Browserless but took a quick look. It seems they're very focused on the scraping use case. We're more focused on the agent use case. One of our first customers turned us on to this - they wanted to build an RPA automation to push data to a cloud EHR. The problem was it ran as a single page application with no URL routing, and had an extremely complex API for their backend that was difficu…
Sounds like a prooblem that can be solved with a Playwright script with a bit of error checking in it. I think this needs more elaboration on what the Finic wrapper is adding to stock Playwright that can't just be achieved through more effective use of stock Playwright.
Re: Show HN: Finic – Open source platform for building browser automations
#74Earlier quoted context omitted.
https://antoinevastel.com
Thanks!
If you were to use an automated browser, such as puppeteer / playwright: - People don't move mouses in "straight" lines.
- People don't click on things that are out of viewport.
- Check the permissions you give sites.
Additional info:
- https://stackoverflow.com/questions/57987585/puppeteer-how-t...
- Look into connecting with CDP.
Re: Show HN: Finic – Open source platform for building browser automations
#75Earlier quoted context omitted.
In this specific scenario, where the project is using *automated Chrome* to even bother with the connection, redirects, and bazillions of other "browser-y" things to arrive at HTML to be parsed, the very idea that one would `soup = BeautifulSoup(playright.content())` is crazypants to me I am open to the fact that html5lib strives to parse correctly, and good for them, but that would be the case where one wished to us…
I think there's some misunderstanding? Sometimes parsing HTML is the best way to get what you need, however there are many situations where one must use something like playwright to get the HTML in the first place (for example, the html is generated clientside by javascript). What's the better alternative?
What I'm saying is that doing the equivalent of
chrome.exe --dump-html https://example.com/lol \
| python -c "import bs4; print('reevaluate life choices that led you here')"
is just facepalm stupid. The first step by definition has already parsed all the html (and associated resources) into a very well formed data structure and then makes available THREE selector languages (DOM, CSS, XPath) to reach into that data structure and pull out the things which interest you. BS4 and its silly python friends implement only a small fraction of those selector languages, poorly. So it's fine if a hammer is all you have, but to launch Chrome and then revert to bs4 is just "what problem are you solving here, friend?"Re: Show HN: Finic – Open source platform for building browser automations
#76I've been working on browser agent the last week[1]. So this is very exciting. There are also browser agent implementations like Skyvern[2] (Also YC backed) ,or Tarsier[3] Seems like, finic is providing a way to scale/schedule these agents? If that's the case what's the advantage over something like airflow or windmill ? If I remember correctly, Skyvern also has an implementation of scaling these browser tasks built…
Cloning into 'tarsier'...
remote: Enumerating objects: 15238, done.
remote: Counting objects: 100% (1613/1613), done.
remote: Compressing objects: 100% (929/929), done.
Receiving objects: 100% (15238/15238), 3.01 GiB | 14.82 MiB/s, done.Re: Show HN: Finic – Open source platform for building browser automations
#77I've been working on browser agent the last week[1]. So this is very exciting. There are also browser agent implementations like Skyvern[2] (Also YC backed) ,or Tarsier[3] Seems like, finic is providing a way to scale/schedule these agents? If that's the case what's the advantage over something like airflow or windmill ? If I remember correctly, Skyvern also has an implementation of scaling these browser tasks built…
Re: Show HN: Finic – Open source platform for building browser automations
#78I've been working on browser agent the last week[1]. So this is very exciting. There are also browser agent implementations like Skyvern[2] (Also YC backed) ,or Tarsier[3] Seems like, finic is providing a way to scale/schedule these agents? If that's the case what's the advantage over something like airflow or windmill ? If I remember correctly, Skyvern also has an implementation of scaling these browser tasks built…
Based on the feedback in this thread we're going to be releasing an updated version that focuses more around tooling for the browser agents themselves as opposed to scaling/scheduling, so stay tuned for that!
Re: Show HN: Finic – Open source platform for building browser automations
#79I've been working on browser agent the last week[1]. So this is very exciting. There are also browser agent implementations like Skyvern[2] (Also YC backed) ,or Tarsier[3] Seems like, finic is providing a way to scale/schedule these agents? If that's the case what's the advantage over something like airflow or windmill ? If I remember correctly, Skyvern also has an implementation of scaling these browser tasks built…
https://github.com/reworkd/tarsier/pull/115/files represents someone who does not know what git is used for Cloning into 'tarsier'... remote: Enumerating objects: 15238, done. remote: Counting objects: 100% (1613/1613), done. remote: Compressing objects: 100% (929/929), done. Receiving objects: 100% (15238/15238), 3.01 GiB | 14.82 MiB/s, done.