Live data from Hacker News

Ryanair wins screen scraping case against Booking.com in US court ruling

rte.ie

21–30 of 303 posts

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#21
post #16

Earlier quoted context omitted.

As I understand it, scraping data read-only is fine (Google Flights, Skyscanner etc) but using automated processes to book tickets on behalf of customers without sending them to the Ryanair site is not fine.

And here I was thinking that read-only was part of the definition of scraping?

The article mentions reselling.

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#22
> A jury in the District Court of Delaware unanimously found that Booking.com violated the Computer Fraud and Abuse act and that it had induced a third party to access parts of Ryanair's website without authorisation "with an intent to defraud," the verdict said

I imagine this is limited to a scenario where you: 1. Act as a middle-man for the transaction (as this lawsuit was about resale), 2. Interfere with pricing or other service aspects, 3. Add your own profit. I don't think this sets any precedent against scraping on its own.

(The highly variable and discriminatory pricing of travel would also best be addressed in regulation, rather than relying entirely on third-party resellers to rescue you.)

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#23

pretty bad precedent, id argue that anything thats publicly accesible is free to be scraped. So unless they did something illegal via bypassing security, then this sets a really bad tone for internet archival, web scraping and data collection in the future.

In fact I wrote my own RyanAir scraper to get the best prices on flights (it is trivial to implement, they barely have any rate limits - in particular if you use the API endpoint where you search for flights departing from a specific airport).

But I guess my scraping is a lot less, as I'm only looking for a few flights

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#24

pretty bad precedent, id argue that anything thats publicly accesible is free to be scraped. So unless they did something illegal via bypassing security, then this sets a really bad tone for internet archival, web scraping and data collection in the future.

As I understand it, scraping data read-only is fine (Google Flights, Skyscanner etc) but using automated processes to book tickets on behalf of customers without sending them to the Ryanair site is not fine.

If the ruling (which I haven't read) says automated booking via screen scraping is illegal: wouldn't a workaround be to replace the automated process with a human in a low-cost country?

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#25

I'm not sure why because Ryanair looks really good on the scrapers. I bet it drives a lot of business their way. That is of course until you add all the additional charges.

You can fly for not a lot of money on Ryanair, their fee structure, website, and app are similar to all other budget airlines. Those extra fees are for handling your luggage (extra manpower and fuel). If you want to complain about Ryanair's fees, get hold of the Fees Schedule for the airport you fly from and to. You will learn how much airports charge for landing, parking, hangarage, handling, fuel, etc. It's an eye-opening read.

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#26
post #16

Earlier quoted context omitted.

As I understand it, scraping data read-only is fine (Google Flights, Skyscanner etc) but using automated processes to book tickets on behalf of customers without sending them to the Ryanair site is not fine.

And here I was thinking that read-only was part of the definition of scraping?

Yeah, it's not a terribly well-written article, and _Ryanair_ is certainly trying to push the line that this is about scraping, but it's hard to imagine that the _resale_ thing wasn't a significant part of the case.

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#27

Earlier quoted context omitted.

As I understand it, scraping data read-only is fine (Google Flights, Skyscanner etc) but using automated processes to book tickets on behalf of customers without sending them to the Ryanair site is not fine.

If the ruling (which I haven't read) says automated booking via screen scraping is illegal: wouldn't a workaround be to replace the automated process with a human in a low-cost country?

That sounds like a very Amazon-esque solution!

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#28

pretty bad precedent, id argue that anything thats publicly accesible is free to be scraped. So unless they did something illegal via bypassing security, then this sets a really bad tone for internet archival, web scraping and data collection in the future.

This lawsuit is not about scraping, it is about booking.com acting as a reseller of ryanair products without a reseller agreement - to which they mention that booking.com adds their own profits to the transaction and makes ryanair unable to communicate with the real customer - through "unauthorized access" (scraping).

What we on hackernews would consider scraping is not covered by this lawsuit, and ryanair's vendetta is not against scraping but "pirate online travel agencies" (resellers).

Re: Ryanair wins screen scraping case against Booking.com in US court ruling

#29

I'm not sure why because Ryanair looks really good on the scrapers. I bet it drives a lot of business their way. That is of course until you add all the additional charges.

Ryanair's claim was that Booking.com etc was reselling its seats, adding its own charges on top, and providing false passenger details. It's in Ryanair's interest to portray this as basically a screen scraping case (because Ryanair don't like screen scraping in general), but there does seem to be more to it than just that.
Post reply on HN