News for hackers. Stuff that matters.
Re:Web Scraping in 2016 by hchasestevens on Tuesday August 23, 2016 @03:06PM (#12346529)
A small counterpoint to this -- in the airline industry, it's relatively commonplace for seat reservations to be made for a user _before_ payment has occurred. In this case, if you're mirroring normal browser activity, you can (temporarily) reduce availability on a flight, potentially even bumping up the price for other, legitimate users, and almost certainly causing the airline to incur costs beyond normal bandwidth and server costs. I'm sure there are many other domains for which this is also the case, however rare.
Re:Web Scraping in 2016 by gnud on Tuesday August 23, 2016 @04:36PM (#12347356)
If they don't do the seat reservation behind a POST, or at least blacklist the reservation page in robots.txt, I have no sympathy.
Re:Web Scraping in 2016 by Steeeve on Tuesday August 23, 2016 @10:36PM (#12349289)
I've had this happen regularly enough that I developed the habit of finding a fare in the morning and then returning at 11pm ready to buy.
Re:Web Scraping in 2016 by Chris2048 on Wednesday August 24, 2016 @07:26AM (#12351203)
Cinemas and some online shops do the same. I've always wondered if it's possible to block any tickets sales for entire flights/screenings/products this way.

And if airline tickets are based on supply v demand, it might even be possible to drive down ticket prices by suddenly dropping a load of blocks near to the flight date.

Re:Web Scraping in 2016 by angry_octet on Wednesday August 24, 2016 @09:57AM (#12352023)
If you have ever tried to buy hot tickets online and not been able to get any, this is due to bots. Bots are the scalpers friend.

This can easily be prevented by requiring ID matching the ticket on entry, but the ticket sellers often don't seem to care.