IMDB Script seems to be not working

[MrObama2022]

Back when AMC started to use scripts, IMDb was not fully against it: as long as it was for personal use and clearly stated that data came from IMDb, it was tolerated. It may of course have changed. Maybe one should search in the legal terms of IMDb if they mention something about that clearly.

https://www.imdb.com/conditions

Robots and Screen Scraping: You may not use data mining, robots, screen scraping, or similar data gathering and extraction tools on this site, except with our express written consent as noted below.

But we are using the official Chrome browser version here. How I access to an official browser, using API, AI or other tools it's up to me, my pc, my rules, my life, my home. Chromedriver is an official Google product, not a warez product. I can also use a routine or an agent AI to perform action on my browser when I'm away from my PC. If I access to a site using Chrome, then I can also use all the functions included in Chrome that is "reading mode", "inspect the code", "save html", use Chrome plugin (like adblock) and access to the browser using api. If you don't like, you can block Chrome user agent on your site. So if I ask copilot to access every day to imdb website using chrome, read the content of the best rated movies and give me a detailed report in a txt file I'm violating imdb conditions?

By the way, I think it's "more compliant" access to imdb using Chrome then using curl or AMC GetPage() function.

I'm not sure that such complicated setup (dependency on external tools to install) is a good idea for an "official" version, but at least it could be used for advanced users.
If applied officially, the script should keep the option (by default) to use GetPage etc. in case IMDb removes the filter/ban (though that it is unlikely...) and when detecting that the servers returns the cloudflare page with javascript, then it could display a message suggesting to enable that option and install needed tools.
I have no idea about the legal concerns about this, but as long as it is not provided as an all-in-one out-of-the-box solution, used only on a small scale for personal use, I suppose it is not the kind of thing that IMDb targets or is even against.

The new default solution for general users should be the API, as long as it works (and the recommendation to use of the API script could also be mentioned in the error message displayed by the IMDb script when it is blocked by cloudflare).

Ok, GetPage() as default and "setup" if fails. I'll work on this.

API are ok but I don't know how long they will stay free

[Dorohedoro]

Back when AMC started to use scripts, IMDb was not fully against it: as long as it was for personal use and clearly stated that data came from IMDb, it was tolerated. It may of course have changed. Maybe one should search in the legal terms of IMDb if they mention something about that clearly.

https://www.imdb.com/conditions

Robots and Screen Scraping: You may not use data mining, robots, screen scraping, or similar data gathering and extraction tools on this site, except with our express written consent as noted below.

But we are using the official Chrome browser version here. How I access to an official browser, using API, AI or other tools it's up to me, my pc, my rules, my life, my home. Chromedriver is an official Google product, not a warez product. I can also use a routine or an agent AI to perform action on my browser when I'm away from my PC. If I access to a site using Chrome, then I can also use all the functions included in Chrome that is "reading mode", "inspect the code", "save html", use Chrome plugin (like adblock) and access to the browser using api. If you don't like, you can block Chrome user agent on your site. So if I ask copilot to access every day to imdb website using chrome, read the content of the best rated movies and give me a detailed report in a txt file I'm violating imdb conditions?

By the way, I think it's "more compliant" access to imdb using Chrome then using curl or AMC GetPage() function.

I'm not sure that such complicated setup (dependency on external tools to install) is a good idea for an "official" version, but at least it could be used for advanced users.
If applied officially, the script should keep the option (by default) to use GetPage etc. in case IMDb removes the filter/ban (though that it is unlikely...) and when detecting that the servers returns the cloudflare page with javascript, then it could display a message suggesting to enable that option and install needed tools.
I have no idea about the legal concerns about this, but as long as it is not provided as an all-in-one out-of-the-box solution, used only on a small scale for personal use, I suppose it is not the kind of thing that IMDb targets or is even against.

The new default solution for general users should be the API, as long as it works (and the recommendation to use of the API script could also be mentioned in the error message displayed by the IMDb script when it is blocked by cloudflare).

Ok, GetPage() as default and "setup" if fails. I'll work on this.

API are ok but I don't know how long they will stay free

But that system is using a public app (AMC) to let a script fake browser activity with the intention of scrapping a site that forbid that behavior and it's actively blocking know methods. And the worst part, you are singing said method in a public forum for them to know (IMDb is reading us right know, I'm sure).

My point telling you this: we should treat this matter privately.