Technical. A Better Queue's database currently takes in only the first genre listed for a movie from the Netflix API. So those other 235 Gay and Lesbian movies are present in A Better Queue, but in other genres. The choice to only take in the first genre listed from the Netflix API was that, beyond trying to keep it simple, the first genre seemed like the most accurate one. The choice was in no way intended to be exclusionary.
I would be able to take in multiple genres during a database load so that each movie could show up for all of its genres. So I will. Right now I'm waiting to hear back from Rotten Tomatoes' API team so I can get a second API key for development. (Using my production key to test new functionality would put me over my API call limit.)
As noted below, I'm teaming with a designer friend of mine for a redesign of ABQ. We'll probably get rid of those JQuery sliders as the don't work well on mobile devices. In any case we'll keep this in mind. Thank you.
Hey everybody. I made this thing. Thanks for posting, xbryanx! It's so cool that my first web app is on the front page of HN.
ADDENDUM::
I'm somewhat new to all of this. Right now I'm learning BDD principles. So, I'm going to use A Better Queue as a learning tool and blog about BDDing new features, like an 'add to instant queue' button. I'll probably blog here: http://abetterqueue.blogspot.com/
After that, I'll re-write ABQ using BDD principles and then I'll open-source the thing.
This is because Rotten Tomatoes uses a more thorough criteria for "Action and Adventure", whereas A Better Queue uses the first Netflix genre criteria that's listed on the result from its api. So yeah, Rotten Tomatoes is more thorough in this regard. Most of the movies listed by Rotten Tomatoes with this criteria are under different genres in A Better Queue.