Super, what I had hoped/expected! thanks.

Just wondering how it works internally does English cover any english variety or only the 'specified' english? If I did say Austrlian English i would expect just that, but for the native one it's hard to say right?

@admin for greece search stuff - ya really weird. i think that's the start of hiding most unique content away. But I finding that even directly accessing stuff trips the proxy error these days - especially in CH/Switzerland. The issue I have run into is that I was just using the UI via Selenium to do some matching up of my library to possible higher resolution options. but that doesn't work if 'searcing hides stuff' oh well. It was a good exercise in refreshing my scraping knowledge.

The 'hiding of country specific titles' seems to be the latest thing to trip 'proxy/vpn' errors. Looks like any content outside your home country, now has a huge chance to trip that error - even in situations where it used to work a few weeks back. Not good for the Netflix VPN scene possibly!!

I was just going to post on this since I looked and I swore last night there was 36, and now 1/2, I can imagine the nightmares involved. I was about to post a bunch of questions on Belgium and others, since the data seemed very stale,, everyhting i tried to search for was not there once I looked. Good luck!!

Shows updated recently, and shows Canada and USA as having it, but it's not valid for either.

How would this be any diffferent than an 'unique' search you already support,or are those canned searches/results? Sorry I work on some databases that process millions of tranactions a day so can see a query that should not be too nasty, but maybe for your db it would be. I am one of the guys that hunts/destroys db deadlocks etc in ms sql for our situation, so optimizing/making things like this work is what I do.

Nope, and/or/unique don't give the option to find everything in say South Korea not in Canada or Usa (where I normally search).

Already has relevance sort, duh! Somehow I missed that, sorry!!!

Basically matching on how much of your search matches the item. So full matches to say 'cell' would come up if it was an exact match, so usually it's number of matching letters/words over whole letters/word count - so percentage etc. REALLY makes the UI come alive vs right now it's a search on each word, which is good - but the 'real match' is oten rows down the screen.