(browserflow.app)

707 points namukang | 1 comments | 17 Nov 21 15:16 UTC | HN request time: 0.472s | source

Show context

moritonal ◴[17 Nov 21 19:33 UTC] No.29257791[source]▶

Whilst nice, how is this going to handle the changing nature of the web? It's nice that it detects "lists" and such, but a few changes to CSS is going to trash that automation right?

I'm also fairly sure you'll break (either directly, or on a user's behalf) a few EULA's that really specifically ban scraping.

replies(2): >>29258424 #>>29260327 #

kreeben ◴[17 Nov 21 20:28 UTC] No.29258424[source]▶

>>29257791 #

Didn't this case [0] set a precedence that "scraping is not against the law" irregardless of EULA?

[0] https://en.wikipedia.org/wiki/HiQ_Labs_v._LinkedIn

replies(4): >>29258469 #>>29258707 #>>29259962 #>>29260430 #

1. wccrawford ◴[17 Nov 21 20:32 UTC] No.29258469[source]▶

>>29258424 #

"using data that is publicly available"

If the user is logged in, that data may not be publicly available, and the EULA would still apply.

↑

Show HN: I made a Chrome extension that can automate any website