1.0.36 website update

UPDATE (Feb 3 2019)
Dynamic reCAPTCHA enabled
A recent server side update has been pushed out that now automatically enables and disables reCAPTCHA as deemed necessary by the risk level determined by incoming connections. This means the entire reCAPTCHA system will be disabled unless suspicious activity is detected that the server cannot mitigate (in which case, reCAPTCHA will activate and you may have to solve a captcha). This means in cases where the server does not see any issues, there will be no reCAPTCHA scripts sent by the server and no verification completed. has been updated to enhance the security and performance of the website. This update is a precursor to the new overhaul of the website, and has two goals: combat bots to improve performance by giving server power to those who need it (humans, i.e. you, the user), as well as server-side enhancements to the caching system.

This update focuses on two new changes to the sites infrastructure and client-side code, and marks one of the final updates of the original website release prior to the overhaul. This update:

Adds reCAPTCHA to the search system
I know, I know, most people aren’t a huge fan of those impromptu quizzes to prove you’re not the worlds greatest artificial intelligence. “Select the traffic lights” aren’t fun, but I’ve decided it’s a necessary addition as I continue to improve the site, especially with the new features coming in the major update. This reCAPTCHA protection applies to the search system on the site (searching for actors/movies/etc) and not individual pages. reCAPTCHA is smart enough that if it trusts you, you shouldn’t even notice this change.
An additional note is visible at the bottom of this post if you’re using an API

Cache enhancement and clearing
The cached data collected over the past few weeks has been reset to prevent issues with any code changes in this push.

API changes
There are no changes to the API with the reCAPTCHA change. We suggest implementing reCAPTCHA on your end, but there are no changes to the actual use of the API itself. No limits and no reCAPTCHA requirement.